[ http://issues.apache.org/jira/browse/GERONIMO-2292?page=all ]
Aaron Mulder updated GERONIMO-2292:
-----------------------------------
Summary: Investigate unused targetConfigId parameter in EJB refs
(was: Investigate unused targetModuleId parameter in EJB refs)
Fix Version/s: 1.1.2
(was: 1.1.1)
David Jencks fixed the main problem in G 1.1.1 with this comment:
Fix in openejb 2.1.1 rev 2823. Still needs review of unused targetConfigId
parameter.
This is a copy of the issue opened to track the "review of unused
targetConfigId" parameter int he post-1.1.1 timeframe.
> Investigate unused targetConfigId parameter in EJB refs
> -------------------------------------------------------
>
> Key: GERONIMO-2292
> URL: http://issues.apache.org/jira/browse/GERONIMO-2292
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: deployment, OpenEJB
> Affects Versions: 1.1
> Reporter: Aaron Mulder
> Assigned To: David Jencks
> Fix For: 1.1.2
>
>
> 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:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
