AbstractEJBReferenceMetaData ejb-link issue

[bdecoste]

The AbstractEJBReferenceMetaData mappedName value seems to be populated from xml when there is no explicit jndi binding but there is an ejb-link value. mappedName is set to the link value. I've made a change to EJBRemoteHandler to work around this. Not sure if this is intention in metadata or not ...

[starksm64]

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.

[alrubinger]

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

[starksm64]

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.