Thanks for your reply, but as far as I can see the naming properties are cached
inside the StatefulHandleImpl at construction-time. So when I call
SessionContext.getEJBObject().getHandle() the handle gets constructed inside
the server JVM. And these properties are still in use when this handle instance
is serialized into the client JVM.
To confirm this in a test environment I switched to the
org.jboss.naming.NamingContextFactory on the client side and called
NamingContextFactory.lastInitialContextEnv.get() to get sure the naming
properties are cached properly. But even though Handle.getEJBObject() results
in the following exception:
java.rmi.RemoteException: Error during getEJBObject; nested exception is:
javax.naming.NameNotFoundException: Name MyBean is not bound in this
Context
Only after I changed default/conf/jndi.properties in my JBoss installation
directory, the handle worked as expected.
Regards,
Lars
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3928249#3928249
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3928249
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
JBoss-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user
