Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Message-ID: <32554605.1190252052985.JavaMail.jira@brutus>
Date: Wed, 19 Sep 2007 18:34:12 -0700 (PDT)
From: "Kevan Miller (JIRA)" <jira@apache.org>
To: dev@geronimo.apache.org
Subject: [jira] Reopened: (GERONIMO-3425) Add deployment plan schemas to
 geronimo web site
In-Reply-To: <627285.1187665416446.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Kevan Miller reopened GERONIMO-3425:
------------------------------------


Well, not quite what I had hoped for... The doc is great. However...

Note how the following url: http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd actually serves the schema.

I was hoping for the equivalent capability for Geronimo deployment plans. This would allow IDE's (e.g. Eclipse) to automatically download the schemas.

May be a bit complicated because of the screwy names we give our schema files... Perhaps just a little indirection would fix this.

> Add deployment plan schemas to geronimo web site
> ------------------------------------------------
>
>                 Key: GERONIMO-3425
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-3425
>             Project: Geronimo
>          Issue Type: Improvement
>      Security Level: public(Regular issues) 
>          Components: website
>            Reporter: Kevan Miller
>            Assignee: Hernan Cunico
>
> I seem to recall this being raised, some time ago. I thought it had been addressed, but does not seem to be the case.
> It's really convenient if the xmlns url would actually contain the schemas for our deployment plans. That way some ide's (e.g. Eclipse) will automatically load the schemas. For example http://geronimo.apache.org/xml/ns/j2ee/application-2.0 should serve the schema for our application deployment plan. 
> We should do the same for OpenEJB (e.g. http://www.openejb.org/xml/ns/openejb-jar-2.1). 
> An overview of our deployment plan schemas at http://geronimo.apache.org/xml/ns/ would also be useful. 
> See http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd and http://java.sun.com/xml/ns/javaee/ for examples how other organizations have handled this...

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.