This content has been marked as final.
Show 3 replies
-
1. Re: AbstractEJBReferenceMetaData ejb-link issue
starksm64 Mar 4, 2008 5:07 PM (in response to bdecoste)The current resolution behavior is overwriting this as this was the only value for the resolved name at the time. A resolvedJndiName has since been added to the base ResourceInjectionMetaData, and this is what should be set and used.
-
2. Re: AbstractEJBReferenceMetaData ejb-link issue
alrubinger Mar 4, 2008 8:03 PM (in response to bdecoste)I've switched the overwrites to instead write the resolved link target to "ref.setResolvedJndiName(target);".
http://fisheye.jboss.org/changelog/JBossAS/?cs=70397
...which will invalidate Bill's change within EJB3, so I reverted that.
On local beans, the link target is resolved to the pattern:"local/" + ejbName + '@' + System.identityHashCode(ejbName);
...in JBossEnterpriseBeanMetaData.determineLocalJndiName(). Not sure if this is desired.
S,
ALR -
3. Re: AbstractEJBReferenceMetaData ejb-link issue
starksm64 Mar 4, 2008 9:44 PM (in response to bdecoste)That form of local jndi name would only be created if not explicitly defined in the metadata. This should be fine as there is no standard for a local jndi name binding or expectation that it has a global jndi binding.