[GERONIMO-2292] Investigate unused targetConfigId parameter in EJB refs

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 1.1
• Fix Version/s: Wish List
• Component/s: deployment, OpenEJB
• Security Level: public (Regular issues)
• Assignee: David Jencks
• Reporter: Aaron Mulder
• Created: 07/Aug/06 15:23
• Updated: 07/Dec/06 19:56

Description

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)

Issue Links

• is a clone of: GERONIMO-2142 EJB Refs to EJB in parent module often fail