[jboss-jira] [JBoss JIRA] Commented: (JBAS-5285) *ReferenceMetadataResolverDeployers overridding explicitly-defined jndi-name

Tue Mar 18 19:08:50 EDT 2008

    [ http://jira.jboss.com/jira/browse/JBAS-5285?page=comments#action_12403508 ] 

Alexey Loubyansky commented on JBAS-5285:
-----------------------------------------

I have it working locally. This will require the next version of jboss-metadata. The issue in metadata is JBMETA-8. I'll commit the fix to the AS once after updating the metadata version in the thirdparty.

> *ReferenceMetadataResolverDeployers overridding explicitly-defined jndi-name
> ----------------------------------------------------------------------------
>
>                 Key: JBAS-5285
>                 URL: http://jira.jboss.com/jira/browse/JBAS-5285
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Andrew Lee Rubinger
>         Assigned To: Alexey Loubyansky
>             Fix For: JBossAS-5.0.0.CR1
>
>
> MappedReferenceMetadataResolverDeployer and ReferenceMetadataResolverDeployer contain methods resolveEjbRefs/resolveEjbLocalRefs which override the mappedName in the metadata objects if an ejb-link is defined.  In this case, the mappedName/jndi-name becomes the resolved JNDI Name referenced by ejb-link.
> Instead, the "resolvedJndiName" property should be set to the address resolved from ejb-link, leaving mappedName/jndi-name intact (it may be declared explicitly).
> This change will have repercussions within EJB2 ,AS TestSuite, and metadata projects.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira