[omniORB] TypeCode Any problems continued

PK padrone.pk at gmail.com
Tue Jun 1 16:52:34 BST 2010

I found a solution, just did not have time to send it to the mailing list.
The problem was caused by the flag tcAliasExpand.
But not just simple that.
I had an omniORB.cfg file, had all environment variable set up correctly. In
the cfg file I had the tcAliasExpand flag set to 0, as it was ment.
In the code I had a recommended code by the guide:
const char* options[][2] = {{"maxGIOPVersion","1.2"},
{"lcdMode","1"},{"clientCallTimeOutPeriod", "0"}, {"traceLevel",
"40"},{"tcAliasExpand","0"}, {0,0} };
orb = CORBA::ORB_init(argc, argv,"omniORB4", options);
Despite in the cfg file, and in the options part set value, in the logs I
could see that the tcAliasExpand is 1.
The solution was to use
orb = CORBA::ORB_init(argc, argv);
and this solved the tcAliasExpand problem, and the problem with alias
interpretation also.

I am struggling with another problem, if I do not find a solution, I will
post it to the mailing list.
Best Regards

2010/6/1 Duncan Grisby <duncan at grisby.org>

> On Tue, 2010-05-18 at 12:00 +0200, PK wrote:
> [...]
> > How can I insert the correct alias information to the request? The
> > server side cannot interpret the request I am sending. Am I
> > misunderstanding something?
> Please come up with an absolutely minimal example that shows the problem
> and post the complete code for it. It's impossible to diagnose anything
> with just small fragments of your code.
> Duncan.
> --
>  -- Duncan Grisby         --
>  -- duncan at grisby.org     --
>   -- http://www.grisby.org --
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.omniorb-support.com/pipermail/omniorb-list/attachments/20100601/dbadb6d6/attachment.htm

More information about the omniORB-list mailing list