[omniORB] Re: omniORB-list Digest, Vol 82, Issue 2

Edward Lin edwardlin.tw at gmail.com
Thu Feb 4 20:59:46 GMT 2010


In addition to set right configurations, your CORBA object must  
support 'persistent object'. You may refer to onmiORB examples for  
more detail technical skills.

Thanks,
Edward Lin

On 2010/2/4, at 20:00, omniorb-list-request at omniorb-support.com wrote:

> Send omniORB-list mailing list submissions to
>    omniorb-list at omniorb-support.com
>
> To subscribe or unsubscribe via the World Wide Web, visit
>    http://www.omniorb-support.com/mailman/listinfo/omniorb-list
> or, via email, send a message with subject or body 'help' to
>    omniorb-list-request at omniorb-support.com
>
> You can reach the person managing the list at
>    omniorb-list-owner at omniorb-support.com
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of omniORB-list digest..."
>
>
> Today's Topics:
>
>   1. Naming Service IP Address (Piccoli, Joseph)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 3 Feb 2010 15:26:09 -0800
> From: "Piccoli, Joseph" <jpiccoli at tnsi.com>
> Subject: [omniORB] Naming Service IP Address
> To: "omniorb-list at omniorb-support.com"
>    <omniorb-list at omniorb-support.com>
> Cc: "Burton, Craig" <crburton at tnsi.com>, "Zhao, Weiguang"
>    <wzhao at tnsi.com>
> Message-ID:
>    <C0C9408742654B429ECD3D1FF11A118D3614D6CB at TNS-MAIL-NA1.win2k.corp.tnsi.com 
> >
>
> Content-Type: text/plain; charset="us-ascii"
>
> Hello all,
>
> I am having a problem creating a NamingContext on Solaris. I create  
> an initial context with the IP address of the machine running the  
> omniNames server, which is not running on the same machine that my  
> omniorb server is running. This works correctly. Next, I try to add  
> a context to the initial context using bind_new_context( ). The  
> response to this contains an IP address which is different from the  
> one associated with the initial context. I do not know if this an  
> omniNames or omniorb issue. Is there a means to force omniNames to  
> always use the same IP address in establishing contexts? I have  
> attempted various settings of the "endPontNoPublish",  
> "endPointNoListen", "clientTransportRule", and "serverTransportRule"  
> settings without success.
>
> Thanks,
> Joe Piccoli
> Software Engineer
> Telecommunication Services Division
> Transaction Network Services, Inc.
> Office: (360) 493-6208 | jpiccoli at tnsi.com<mailto:jpiccoli at tnsi.com>
>
>
> ________________________________
> This e-mail message is for the sole use of the intended recipient(s) 
> and may
> contain confidential and privileged information of Transaction  
> Network Services.
> Any unauthorised review, use, disclosure or distribution is  
> prohibited. If you
> are not the intended recipient, please contact the sender by reply e- 
> mail and destroy all copies of the original message.
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: http://www.omniorb-support.com/pipermail/omniorb-list/attachments/20100203/33c22375/attachment-0001.htm
>
> ------------------------------
>
> _______________________________________________
> omniORB-list mailing list
> omniORB-list at omniorb-support.com
> http://www.omniorb-support.com/mailman/listinfo/omniorb-list
>
>
> End of omniORB-list Digest, Vol 82, Issue 2
> *******************************************



More information about the omniORB-list mailing list