[
https://issues.apache.org/jira/browse/GERONIMO-4237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12628692#action_12628692
]
David Blevins commented on GERONIMO-4237:
-----------------------------------------
That would explain why this didn't come up in the openejb build as there the
deploymentId defaults to the ejbName, so these two are functionally the same:
EjbDeployment deployment = ejbds.get(info.ejbName);
EjbDeployment deployment = ejbds.get(info.ejbDeploymentId);
So theoretically there is a workaround for any 2.1.x Geronimo release. The
user can set the "openejb.deploymentId.format" system property to the value
"{ejbName}".
-Dopenejb.deploymentId.format={ejbName}
This will have other limitations as the deploymentId is required to be globally
unique in the entire server, so no two beans will be able to share the same
ejbName.
Manu, assigning this to you as you did all the foot work on it. Open up
another jira issue in the OpenEJB jira, to make sure it gets in the release
notes, titled "Element <jndi> possibly ignored in openejb-jar.xml" and link it
to this one.
> Elements <jndi-name>, <jndi-local-name> and <jndi> ignored in openejb-jar.xml
> -----------------------------------------------------------------------------
>
> Key: GERONIMO-4237
> URL: https://issues.apache.org/jira/browse/GERONIMO-4237
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: naming, OpenEJB
> Affects Versions: 2.0, 2.0.1, 2.0.2, 2.1, 2.1.1, 2.1.2
> Reporter: David Blevins
> Assignee: David Blevins
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
