[omniORB] Persistence Problem with Corbalocs

[Wernke zur Borg]

I am not quite sure about your problem, but if you already use the
omniINSPOA, why do you stringify your IORs?
 
Use a simple object key, activate_object_with_id() on the server and
corbaloc::<host>:<port>/<key> on the client. No need to stringify anything.
This works fine for me.
 
Wernke

  _____  

From: omniorb-list-bounces at omniorb-support.com
[mailto:omniorb-list-bounces at omniorb-support.com] On Behalf Of joe
Sent: 17 September 2004 00:33
To: 'Omniorb'
Subject: [omniORB] Persistence Problem with Corbalocs


All,
 
I have a persistent servant (using insPOA) that prints its IOR string using
orb.object_to_string.  The servant behaves persistently if I use the IOR
that is printed by the servant in my client by using an orb.string_to_object
and a _narrow.  I am able to kill the servant application and bring it back
and the client object reference is able to access the object when the
servant comes back.  The client object reference works until I kill the
servant and never comes back when the servant is restarted if I use a
corbaloc in the client.  I printed the IOR in the client that is obtained
from the corbaloc and an object_to_string and it is different from the IOR
that the servant outputs.
Any insight would be appreciated.
 
Thanks and Regards,
Joe
 
Joe Wilhelmi
RTLogic
719.598.2801 ext 1162
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.omniorb-support.com/pipermail/omniorb-list/attachments/20040917/0756cd22/attachment-0001.htm