[
https://jira.jboss.org/jira/browse/JBMETA-79?page=com.atlassian.jira.plug...
]
Scott M Stark updated JBMETA-79:
--------------------------------
JBoss Forum Reference:
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4166045
The test which shows the problem is
org.jboss.test.metadata.jbmeta42.unit.Default2xNamingStrategyTestCase.testRemoteHomeWithEarScope.
determineResolvedJndiName for a 2x ejb home returns
----------------------------------------------------
Key: JBMETA-79
URL:
https://jira.jboss.org/jira/browse/JBMETA-79
Project: JBoss Metadata
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 1.0.0.Beta30
Reporter: Scott M Stark
Assignee: Scott M Stark
Fix For: 1.0.0.CR1
If one calls JBossEnterpriseBeanMetaData.determineResolvedJndiName(String) with an ejb2x
remote home iface, for an TestBean ejb in an appclient_dep_compat12_13.ear, the resulting
home jndi name is appclient_dep_compat12_13/TestBean rather than the
appclient_deploy_compat12_13_TestBean jndiName that has been specified via the xml
descriptor/metadata. The logic for remote homes is wrong for ejb2x deployments.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira