You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org> on 2006/06/22 15:38:29 UTC
[jira] Created: (GERONIMO-2142) EJB Refs to EJB in parent module
often fail
EJB Refs to EJB in parent module often fail
-------------------------------------------
Key: GERONIMO-2142
URL: http://issues.apache.org/jira/browse/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:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-2142) EJB Refs to EJB in parent module
often fail
Posted by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2142?page=comments#action_12423393 ]
Aaron Mulder commented on GERONIMO-2142:
----------------------------------------
I would really appreciate it if this could be addressed for 1.1.1. Thanks.
> EJB Refs to EJB in parent module often fail
> -------------------------------------------
>
> Key: GERONIMO-2142
> URL: http://issues.apache.org/jira/browse/GERONIMO-2142
> 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.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: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-2142) EJB Refs to EJB in parent module
often fail
Posted by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2142?page=all ]
Aaron Mulder updated GERONIMO-2142:
-----------------------------------
Assign To: (was: Aaron Mulder)
> EJB Refs to EJB in parent module often fail
> -------------------------------------------
>
> Key: GERONIMO-2142
> URL: http://issues.apache.org/jira/browse/GERONIMO-2142
> Project: Geronimo
> Type: Bug
> Security: public(Regular issues)
> Components: OpenEJB, deployment
> Versions: 1.1
> Reporter: 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:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-2142) EJB Refs to EJB in parent module
often fail
Posted by "David Jencks (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2142?page=comments#action_12423843 ]
David Jencks commented on GERONIMO-2142:
----------------------------------------
Fix in openejb 2.1.1 rev 2823. Still needs review of unused targetConfigId parameter.
> EJB Refs to EJB in parent module often fail
> -------------------------------------------
>
> Key: GERONIMO-2142
> URL: http://issues.apache.org/jira/browse/GERONIMO-2142
> 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.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: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-2142) EJB Refs to EJB in parent module
often fail
Posted by "David Jencks (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2142?page=all ]
David Jencks updated GERONIMO-2142:
-----------------------------------
Attachment: ejbref.src.jar
Previous patch seems to have wrong parents indicated in the ejb, ejb2, and war modules. Hopefully this time I got it right.
> EJB Refs to EJB in parent module often fail
> -------------------------------------------
>
> Key: GERONIMO-2142
> URL: http://issues.apache.org/jira/browse/GERONIMO-2142
> 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.1
>
> Attachments: ejbref-itests.jar, ejbref.src.jar
>
>
> 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
[jira] Updated: (GERONIMO-2142) EJB Refs to EJB in parent module
often fail
Posted by "David Jencks (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2142?page=all ]
David Jencks updated GERONIMO-2142:
-----------------------------------
Fix Version/s: 1.1.1
(was: 1.1.x)
Assignee: David Jencks
I'll see if I can figure out what's going on here and fix it.
> EJB Refs to EJB in parent module often fail
> -------------------------------------------
>
> Key: GERONIMO-2142
> URL: http://issues.apache.org/jira/browse/GERONIMO-2142
> 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.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: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-2142) EJB Refs to EJB in parent module
often fail
Posted by "David Jencks (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2142?page=all ]
David Jencks updated GERONIMO-2142:
-----------------------------------
Attachment: ejbref-itests.jar
Sample applications to demonstrate that ejb-refs between a war and an ejb-jar work. See README for instructions.
> EJB Refs to EJB in parent module often fail
> -------------------------------------------
>
> Key: GERONIMO-2142
> URL: http://issues.apache.org/jira/browse/GERONIMO-2142
> 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.1
>
> Attachments: ejbref-itests.jar
>
>
> 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
[jira] Updated: (GERONIMO-2142) EJB Refs to EJB in parent module
often fail
Posted by "Alan Cabrera (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2142?page=all ]
Alan Cabrera updated GERONIMO-2142:
-----------------------------------
Fix Version/s: 1.1.x
(was: 1.1.1)
Moving unassigned issues over to the 1.1.x pool where they can be worked on for the, in all probability, 1.1.2 patch.
> EJB Refs to EJB in parent module often fail
> -------------------------------------------
>
> Key: GERONIMO-2142
> URL: http://issues.apache.org/jira/browse/GERONIMO-2142
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: deployment, OpenEJB
> Affects Versions: 1.1
> Reporter: Aaron Mulder
> Fix For: 1.1.x
>
>
> 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
[jira] Resolved: (GERONIMO-2142) EJB Refs to EJB in parent module
often fail
Posted by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2142?page=all ]
Aaron Mulder resolved GERONIMO-2142.
------------------------------------
Resolution: Fixed
Closing as resolved in 1.1.1. Copied the issue for investigating the targetConfigId parameter.
> EJB Refs to EJB in parent module often fail
> -------------------------------------------
>
> Key: GERONIMO-2142
> URL: http://issues.apache.org/jira/browse/GERONIMO-2142
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: OpenEJB, deployment
> Affects Versions: 1.1
> Reporter: Aaron Mulder
> Assigned To: David Jencks
> Fix For: 1.1.1
>
> Attachments: ejbref-itests.jar
>
>
> 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