From: <lk...@us...> - 2007-06-21 12:06:41
|
Hi Sylvia, On 6/20/07, Biermann, Sylvia wrote: > after portation of our application form VisiBroker to OpenORB we have a > problem. > > We transfer an object "Session" from one Java application to another. > With VisiBroker we only call > > boa.obj_is_ready(Session); > > within the method creating the session and it worked. > This caused problems with OpenORB and we added > > boa.connect(Session). > > > Now it works generally, but sometimes message invocation at the > "Session"-object causes a NullPointerException. It seems to me, as the > object is getting invalid within the ORB. I have never used BOA (also known as the "Bad Object Adapter"), as it was already deprecated when I started using CORBA. See a message from Doug Schmidt, creator of TAO (one of the leading C++ ORBs) from 2002: http://groups.google.com/group/comp.object.corba/msg/96ba4370d89ece93 POA has been preferred for many many years now, so if you are still using BOA, you are likely to use OpenORB code that is not very robust because nobody else is using it. I think other open source ORBs like Jacorb or Apache Yoko don't even claim to support BOA. I would definitely investigate whether porting your application to POA is an option. That would bring you into "mainstream" mode again: You would use the same code that everyone else uses, and you would have more strategic options, including the switching to an ORB implementation with a broader developer community, like Yoko. > Is this possible? Entirely. Do you have a stacktrace? > Kind regards, > Sylvia Biermann ... > D-21079 Hamburg Hey, finally a user from the Hamburg area, not too far away from where I live. Cheers, Lars |