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

Hernan Cunico commented on GERONIMO-3425:
-----------------------------------------

So, having the actual xsd file available from something like 
http://geronimo.apache.org/xml/ns/j2ee/geronimo-web-2.0.xsd for instance 
instead of 
http://svn.apache.org/repos/asf/geronimo/site/trunk/docs/schemas-2.0/geronimo-web-2.0.xsd
 would do the trick ;-)

Would something like this work (check the links)
h3. JEE Deployment Plans

||Module Type                                           ||Geronimo Schema       
                                                                                
                                                                                
||Preferred Java EE Schema||
|General (Tomcat or Jetty) Web Application (WAR)        
|[http://geronimo.apache.org/xml/ns/j2ee/geronimo-web-2.0.xsd]                  
                        
|[web-app_2_5.xsd|http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd]|
|Tomcat-Only Web Application (WAR)                      
|[http://geronimo.apache.org/xml/ns/j2ee/web/geronimo-tomcat-2.0.xsd]           
                        
|[web-app_2_5.xsd|http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd]|
|Jetty-Only Web Application (WAR)                       
|[http://geronimo.apache.org/xml/ns/j2ee/web/geronimo-jetty-2.0.xsd]            
                        
|[web-app_2_5.xsd|http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd]|
|EJB (JAR)                                              
|[http://www.openejb.org/xml/ns/openejb-jar-2.1|http://svn.apache.org/repos/asf/geronimo/site/tags/pre-confluence/docs/schemas-1.1/openejb-jar-2.1.xsd]
                                 
|[ejb-jar_3_0.xsd|http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd]|
|J2EE Connector (RAR)                                   
|[http://geronimo.apache.org/xml/ns/j2ee/geronimo-connector-1.2.xsd]            
                        
|[connector_1_5.xsd|http://java.sun.com/xml/ns/j2ee/connector_1_5.xsd]|
|Application Client (JAR)                               
|[http://geronimo.apache.org/xml/ns/j2ee/geronimo-application-client-2.0.xsd]   
                        
|[application-client_5.xsd|http://java.sun.com/xml/ns/javaee/application-client_5.xsd]|
|Application (EAR)                                      
|[http://geronimo.apache.org/xml/ns/j2ee/geronimo-application-2.0.xsd]          
                        
|[application_5.xsd|http://java.sun.com/xml/ns/javaee/application_5.xsd]|



> 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.

Reply via email to