geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron Mulder (JIRA)" <>
Subject [jira] Created: (GERONIMO-2142) EJB Refs to EJB in parent module often fail
Date Thu, 22 Jun 2006 13:38:29 GMT
EJB Refs to EJB in parent module often fail

         Key: GERONIMO-2142
     Project: Geronimo
        Type: Bug
    Security: public (Regular issues) 
  Components: deployment, OpenEJB  
    Versions: 1.1    
    Reporter: Aaron Mulder
 Assigned to: Aaron Mulder 
     Fix For: 1.1.1

In OpenEJBReferenceBuilder:

createEJBLocalRef and createEJBRemoteRef accept a targetConfigId argument.

Then they often call getMatch or getImplicitMatch and don't use the targetConfigId.  As a
result, the current module's ID is always used as the targetConfigId:

context.findGBeans(new AbstractNameQuery(context.getId(), ...

This means that the query will never match EJBs in a parent of the current configuration.
 It should be changed to use the targetConfigId instead of the current module's ID.

This does not come up if a pattern element is used in the mapping, though that mapping strategy
runs into a different 1.1 bug (ClassCastException on org.openejb.proxy.ProxyInfo)

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message