[omniORB] POA/BOA IOR compatibility

[Peter Rapier]

The problem we had was that our omniOrb 2.6 server object's IOR did not work
with a client based on BEA's M3.  It did string_to_object but using the
object reference did not work. We wound up bootstrapping the object another
way.
The other things we are hearing I can not verify, but I do know there are
some users (of our products) under the general belief that POA based orbs
won't interoperate with our omniorb 2.6 server.  We do not need any of the
POA enhancements. Our concern is interoperability.  I am investigating the
IOR issue in light of the above.
Thank you.
Peter


 One thing that would be very useful is the corbaloc URL for bootstrapping
purposes.

-----Original Message-----
From: Duncan Grisby [mailto:dgrisby@uk.research.att.com]
Sent: Friday, January 12, 2001 3:34 AM
To: Peter Rapier
Cc: 'omniorb-list@uk.research.att.com'
Subject: Re: [omniORB] POA/BOA IOR compatibility 


On Tuesday 9 January, Peter Rapier wrote:

> We are hearing that clients created with POA based ORB's are having
problems
> understanding a persistent IOR we create on our omniORB 2.6 - based
server.
> It is my understanding that clients should be able to talk to our BOA
based
> orb regardless of their ORB's object adapter and that IOR's have a
specified
> format.  Why would there be a problem with one ORB parsing or otherwise
> understanding anothers ORB's IOR?  Any info that can be shared with me on
> this topic would be greatly appreciated.

There should be no problem with using an IOR from any ORB with any
version of omniORB. POAs and BOAs don't come into it. What error are
you getting?

Cheers,

Duncan.

-- 
 -- Duncan Grisby  \  Research Engineer  --
  -- AT&T Laboratories Cambridge          --
   -- http://www.uk.research.att.com/~dpg1 --