You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Ivan (JIRA)" <ji...@apache.org> on 2011/09/22 09:59:26 UTC
[jira] [Created] (GERONIMO-6169) Recursive lookup while the default
comp entry is configured
Recursive lookup while the default comp entry is configured
-----------------------------------------------------------
Key: GERONIMO-6169
URL: https://issues.apache.org/jira/browse/GERONIMO-6169
Project: Geronimo
Issue Type: Bug
Security Level: public (Regular issues)
Components: deployment
Affects Versions: 3.0-M1
Reporter: Ivan
Assignee: Ivan
Fix For: 3.0
If there is an resource entry like java:comp/EJBContext configured in the DD or added by other modules, and the responsible module has not processed it, AdminObjectRefBuilder will add a JndiReference in the binding map, which will cause the infinite lookup.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-6169) Recursive lookup while the
default comp entry is configured
Posted by "Ivan (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-6169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ivan resolved GERONIMO-6169.
----------------------------
Resolution: Fixed
Think that this should be fixed now.
> Recursive lookup while the default comp entry is configured
> -----------------------------------------------------------
>
> Key: GERONIMO-6169
> URL: https://issues.apache.org/jira/browse/GERONIMO-6169
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: deployment
> Affects Versions: 3.0-M1
> Reporter: Ivan
> Assignee: Ivan
> Fix For: 3.0
>
>
> If there is an resource entry like java:comp/EJBContext configured in the DD or added by other modules, and the responsible module has not processed it, AdminObjectRefBuilder will add a JndiReference in the binding map, which will cause the infinite lookup.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-6169) Recursive lookup while the
default comp entry is configured
Posted by "Ivan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-6169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13112396#comment-13112396 ]
Ivan commented on GERONIMO-6169:
--------------------------------
Commit first step changes to trunk at r1173982. It looks to me that the name should be first checked, if it is the default comp name, we should not create a JndiReference, and leave other modules processed it.
> Recursive lookup while the default comp entry is configured
> -----------------------------------------------------------
>
> Key: GERONIMO-6169
> URL: https://issues.apache.org/jira/browse/GERONIMO-6169
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: deployment
> Affects Versions: 3.0-M1
> Reporter: Ivan
> Assignee: Ivan
> Fix For: 3.0
>
>
> If there is an resource entry like java:comp/EJBContext configured in the DD or added by other modules, and the responsible module has not processed it, AdminObjectRefBuilder will add a JndiReference in the binding map, which will cause the infinite lookup.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira