Hello,

I have run into an interesting problem and would appreciate others
opinion on it.  I'm running Orion 1.4.4 on NT4.0SP6a.

Here's the setup.  Class Flag has a static initializer that accesses a
SessionBean to initialize some static state.  In a client, if I access
the class (and thereby cause the static initializer to be executed),
everything works fine.  However, if the client has not caused the class
to be loaded and another call to Orion causes an instance of Flag to be
serialized to the client the static initializer fails.  It seems that
when the class is loaded during deserialization, the call to
SessionHome.create() (in the static initializer) returns a null and does
_not_ throw any exceptions.

Am I missing something?  Is it illegal to access EJB in such a manner?
Or is this potentially a bug in Orion's serialization/deserialization
mechanism?  Please help!  The obvious workaround is to force the class
to be loaded in the application upon startup.  However, that introduces
an unenforceable requirement on the application clients.

Thanks,
Vidur




Reply via email to