geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ivan (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (GERONIMO-6048) Move geronimo-naming.xsd and geronimo-application.xsd file to j2ee/geronimo-j2ee-schema module
Date Fri, 08 Jul 2011 06:33:16 GMT

     [ https://issues.apache.org/jira/browse/GERONIMO-6048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Ivan resolved GERONIMO-6048.
----------------------------

    Resolution: Fixed

> 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

        

Mime
View raw message