without the code i can only guess. here are some shots at it:
you might not be starting at the root context when resolving. What CORBA implementation(s) are you using?
When you resolve a client in your server you get the reference of the client. When you then chage the reference in the naming Service by calling rebind you are not changing it in the server. As i understand it you will have to resolve the client again for the server to get the new reference...
areza123, thats not what i meant. I mean to pass the IOR to another pc not using the naming service is not straightforward, since you either have to use a common file system or pass the file via ftp (or any other way).
When you are on the same machine using the ior is the simplest way.
If...
Any client or server has to register with the notification service and get the proxySupplier or proxyConsumer from the notification service to be able to push or pull (or get pushed or pulled) events. And especially with the notification service a supplier has to publish the events it provides...
There are many ways to find your servant Objects (when they are not running on the same machine) You can save your IOR into a file pass the file to the client machine and use it as input to your client application. Or you can register your servant in a naming service and the client will get the...
Hi pikoll,
according to OMG and CORBA specification it should be possible for any OMG compliant orb to interoperate with any other. So if OpenORB is OMG compliant this should work.
An open source ORB for c++ including Notification service is the TAO (the ace orb). I use it together with Jacorb...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.