You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "David Jencks (JIRA)" <ji...@apache.org> on 2006/12/07 20:56:23 UTC
[jira] Updated: (GERONIMO-2292) Investigate unused targetConfigId
parameter in EJB refs
[ http://issues.apache.org/jira/browse/GERONIMO-2292?page=all ]
David Jencks updated GERONIMO-2292:
-----------------------------------
Fix Version/s: Wish List
(was: 1.1.2)
> 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: Wish List
>
>
> 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