Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Date: Thu, 22 Sep 2011 08:03:26 +0000 (UTC)
From: "Ivan (JIRA)" <jira@apache.org>
To: dev@geronimo.apache.org
Message-ID: 
 <910509060.1303.1316678606214.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1638380603.1293.1316678366076.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (GERONIMO-6169) Recursive lookup while the
 default comp entry is configured
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ 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