Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Date: Wed, 6 Jul 2011 00:46:18 +0000 (UTC)
From: "Ivan (JIRA)" <jira@apache.org>
To: dev@geronimo.apache.org
Message-ID: 
 <354313216.2357.1309913178059.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Created] (GERONIMO-6048) Move geronimo-naming.xsd and
 geronimo-application.xsd file to j2ee/geronimo-j2ee-schema module
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Move geronimo-naming.xsd and geronimo-application.xsd file to j2ee/geronimo-j2ee-schema module 
-----------------------------------------------------------------------------------------------

                 Key: GERONIMO-6048
                 URL: https://issues.apache.org/jira/browse/GERONIMO-6048
             Project: Geronimo
          Issue Type: Bug
      Security Level: public (Regular issues)
          Components: deployment
    Affects Versions: 3.0
            Reporter: Ivan
            Assignee: Ivan
             Fix For: 3.0


I just found that we do not have schema configuration for jndi reference in geronimo-application.xml file, while trying to add naming:jndiEnvironmentRefsGroup in it, there might be a cycle dependency here,  
geronimo-naming-builder depends on geronimo-j2ee-builder in the past, and if I adds the jndi references in the geronimo-application.xsd, it is required that geronimo-j2ee-builder depends on geronimo-naming-builder ....
I am thinking to move both the schema files to geronimo-j2ee-schema module.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira