Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
1.1
-
Security Level: public (Regular issues)
-
None
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)
Attachments
Attachments
Issue Links
- incorporates
-
GERONIMO-2120 Can't have ejb references outside current config. ClassCastException on org.openejb.proxy.ProxyInfo
- Closed
- is cloned by
-
GERONIMO-2292 Investigate unused targetConfigId parameter in EJB refs
- Open