[
http://jira.jboss.com/jira/browse/JBAS-3967?page=comments#action_12349559 ]
Carlo de Wolf commented on JBAS-3967:
-------------------------------------
For now I have modifed the javaURLContextFactory to automatically lookup 'env' sub
context if it is available and work from there.
EJB3 client enc contains env, J2EE 1.4 doesn't
----------------------------------------------
Key: JBAS-3967
URL:
http://jira.jboss.com/jira/browse/JBAS-3967
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: EJB3
Affects Versions: JBossAS-5.0.0.Beta1
Reporter: Carlo de Wolf
Assigned To: Carlo de Wolf
Fix For: JBossAS-5.0.0.Beta2
The old client application deployer binds entries & references under
<client-name>/, while the EJB3 client deployer binds under <client-name>/env/.
This is because of the common injection framework used in EJB3 both by client deployer and
EJB3 deployer.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira