I found the answer in the following link:
http://www.jboss.org/wiki/Wiki.jsp?page=ClassLoadingConfiguration
which seems to be a pretty much spot-on.
The missing bit was in our config was in
jboss-3.2.5\server\default\conf\jboss-service.xml -
<!-- EAR deployer, remove if you are not using Web layers -->
mbean code="org.jboss.deployment.EARDeployer"
name="jboss.j2ee:service=EARDeployer"
attribute name="Isolated">true</attribute
attribute name="CallByValue">true</attribute
After including the "Isolated" and "CallByValue" attributes, the Ejb Jndi
lookup now works.
There was also a mistake in the jndi-name published in the post - the port
number should have been appended to "localhost".
The Wiki page indicates there is a performance penalty for using "call by
Value", but at least the client code runs unchanged.
Thanks.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3866599#3866599
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3866599
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
JBoss-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user
