Some detail about this fix: when using DeployerEjb and deploying a webapp we start deploying the webapp as a standalone app then we run tomcat which get back the AppInfo
that's fine since no lookup relies on tomcat JNDI tree otherwise the binding doesn't exist at this moment. That's the ifrst issue. The second one was the Deployer being an EJB the JNDI tree retrieved was the ejb one (where the app being deployed was the expected one). The fix simply fix the second part. The first part will be fixed after the release (see my other mail). Note: not using the DeployerEjb all is fine ;) *Romain Manni-Bucau* *Twitter: @rmannibucau* *Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* ---------- Forwarded message ---------- From: Romain Manni-Bucau (JIRA) <j...@apache.org> Date: 2012/9/28 Subject: [jira] [Closed] (TOMEE-434) when using DeployerEjb the JNDI tree is the DeployerEjb one and not the deployed app one To: comm...@openejb.apache.org [ https://issues.apache.org/jira/browse/TOMEE-434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel] Romain Manni-Bucau closed TOMEE-434. ------------------------------------ Resolution: Fixed > when using DeployerEjb the JNDI tree is the DeployerEjb one and not the deployed app one > ---------------------------------------------------------------------------------------- > > Key: TOMEE-434 > URL: https://issues.apache.org/jira/browse/TOMEE-434 > Project: TomEE > Issue Type: Bug > Reporter: Romain Manni-Bucau > Fix For: 1.5.0 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
