[
https://issues.apache.org/jira/browse/GERONIMO-2831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jencks updated GERONIMO-2831:
-----------------------------------
Assignee: Dain Sundstrom (was: David Jencks)
I fixed this in rev 507194 but I'd like dain to review this. In particular I
have no idea what this code in EjbDeployment does and whether it's compatible
with my fix:
if (componentContext != null) {
javaCompSubContext.bind("geronimo", componentContext);
}
> openejb3 installs jndi context rooted at the wrong place
> --------------------------------------------------------
>
> Key: GERONIMO-2831
> URL: https://issues.apache.org/jira/browse/GERONIMO-2831
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Affects Versions: 2.0-M2
> Reporter: David Jencks
> Assigned To: Dain Sundstrom
> Fix For: 2.0-beta1
>
>
> GeronimoThreadContextListener is installing the jndi context from openejb
> into the geronimo root context. However, the openejb context has entries
> starting with java:comp whereas the root context expects the java:comp to be
> stripped off. As a result nothing can be looked up in the java:comp
> namespace.
> // Get the jndi context
> Context jndiContext = ejbDeployment.getComponentContext();
> try {
> jndiContext = (Context) jndiContext.lookup("java:comp");
> } catch (NamingException e) {
> throw new IllegalStateException("jndiContext did not contain
> expected java:comp subcontext", e);
> }
> fixes the problem, but this lookup should be done only once wen the
> ejbDeployment is started.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
