[jboss-dev-forums] [Design of EJB 3.0] - Re: jndi name issues
scott.stark@jboss.org
do-not-reply at jboss.com
Tue Apr 29 14:43:36 EDT 2008
"wolfc" wrote :
| We must have a notion of parent deployment units at metadata level, because else we'll have a problem with the persistence unit deployer (EJB3 Persisitence 6.2.2 Persistence Unit Scope).
|
We have that in the form of the EjbDeploymentSummary.
"wolfc" wrote :
| "scott.stark at jboss.org" wrote : For 3 we need a utility class that properly looks at the reference type to determine if this is a home/local-home, remote or local, business interface lookup.
| Not really, you can just lookup "[ejbName]/[interface]".
|
Then your not considering overrides form other sources such as annotations or xml. A binding of the form "[ejbName]/[interface]" is not going to be unique within an ear let alone the server.
If your talking about a "[ejbName]/[interface]" key against the JBossEnterpriseBeanMetaData:
| @XmlTransient
| public String getJndiName(String ejbName, String iface)
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4147616#4147616
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4147616
More information about the jboss-dev-forums
mailing list