m***@hotmail.com
2006-09-28 14:27:57 UTC
We are currently migrating an application that uses RMI/IIOP to BEA
WebLogic 8.1 SP6. The surprising thing we are currently facing is that
we receive NO_IMPLEMENT exceptions whenever we try to transmit a null
reference.
Digging out our CORBA experience we tried to create an explict NIL
object reference from the well-known OBJECT_NIL IOR. When doing this,
like
org.omg.CORBA.Object nil =
orb.string_to_object( "IOR:00000000000000010000000000000000" );RMI
then this also results in a NO_IMPLEMENT exception.
We Googled a lot, but couldn't find any relevant information, which is
also a surprise. If BEA had such a catastrophic defect, how can it be
that we are the only ones that experiencing it?
The question is whether we are doing something wrong? The code sample
above is simple enough to be sure that we make no coding error. Is
there any special property that explicitly needs to be set to activate
support for null references on BEA? The BEA docs simply state that
IIOP is supported.
Thanks for hints,
Michael.
WebLogic 8.1 SP6. The surprising thing we are currently facing is that
we receive NO_IMPLEMENT exceptions whenever we try to transmit a null
reference.
Digging out our CORBA experience we tried to create an explict NIL
object reference from the well-known OBJECT_NIL IOR. When doing this,
like
org.omg.CORBA.Object nil =
orb.string_to_object( "IOR:00000000000000010000000000000000" );RMI
then this also results in a NO_IMPLEMENT exception.
We Googled a lot, but couldn't find any relevant information, which is
also a surprise. If BEA had such a catastrophic defect, how can it be
that we are the only ones that experiencing it?
The question is whether we are doing something wrong? The code sample
above is simple enough to be sure that we make no coding error. Is
there any special property that explicitly needs to be set to activate
support for null references on BEA? The BEA docs simply state that
IIOP is supported.
Thanks for hints,
Michael.