You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Kevan Miller (JIRA)" <ji...@apache.org> on 2007/08/21 05:03:36 UTC
[jira] Created: (GERONIMO-3425) Add deployment plan schemas to
geronimo web site
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
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.
[jira] Commented: (GERONIMO-3425) Add deployment plan schemas to
geronimo web site
Posted by "Hernan Cunico (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12529895 ]
Hernan Cunico commented on GERONIMO-3425:
-----------------------------------------
Target namespace and actual schema file names are not the same.
For example geronimo-web-2.0.xsd -> targetNamespace="http://geronimo.apache.org/xml/ns/j2ee/web-2.0"
Ideas to make them match?
Cheers!
Hernan
> 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.
[jira] Reopened: (GERONIMO-3425) Add deployment plan schemas to
geronimo web site
Posted by "Kevan Miller (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Resolved: (GERONIMO-3425) Add deployment plan schemas to
geronimo web site
Posted by "Hernan Cunico (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hernan Cunico resolved GERONIMO-3425.
-------------------------------------
Resolution: Fixed
Updated updated with XML Schemas for 1.0, 1.1 and 2.0
http://geronimo.apache.org/xml-schemas.html
Cheers!
Hernan
> 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.
[jira] Assigned: (GERONIMO-3425) Add deployment plan schemas to
geronimo web site
Posted by "Hernan Cunico (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hernan Cunico reassigned GERONIMO-3425:
---------------------------------------
Assignee: Hernan Cunico
> 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.
[jira] Commented: (GERONIMO-3425) Add deployment plan schemas to
geronimo web site
Posted by "Hernan Cunico (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12529169 ]
Hernan Cunico commented on GERONIMO-3425:
-----------------------------------------
Would something like this would work instead of .../xml/ns/j2ee/...
http://geronimo.apache.org/schemas-2.0/...xsd
http://geronimo.apache.org/schemas-1.1/...xsd
http://geronimo.apache.org/schemas-1.0/...xsd
This way we can still serve these files separated by release.
Thoughts?
> 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.
[jira] Commented: (GERONIMO-3425) Add deployment plan schemas to
geronimo web site
Posted by "Jarek Gawor (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12525602 ]
Jarek Gawor commented on GERONIMO-3425:
---------------------------------------
Hernan,
I just added a bunch of the 2.0 schema files. You should be able to update the website now.
> 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
>
> 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.
[jira] Closed: (GERONIMO-3425) Add deployment plan schemas to
geronimo web site
Posted by "Hernan Cunico (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hernan Cunico closed GERONIMO-3425.
-----------------------------------
Resolved.
> 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.
[jira] Commented: (GERONIMO-3425) Add deployment plan schemas to
geronimo web site
Posted by "Hernan Cunico (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (GERONIMO-3425) Add deployment plan schemas to
geronimo web site
Posted by "Hernan Cunico (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12524809 ]
Hernan Cunico commented on GERONIMO-3425:
-----------------------------------------
If we can copy all our schemas to https://svn.apache.org/repos/asf/geronimo/site/trunk/docs/schemas-2.0/ for instance I can update the web site really quick. We already have the schemas for 1.0 and 1.1 on a similar structure.
Volunteers for moving the schemas?
Cheers!
Hernan
> 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
>
> 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.
[jira] Commented: (GERONIMO-3425) Add deployment plan schemas to
geronimo web site
Posted by "Hernan Cunico (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531617 ]
Hernan Cunico commented on GERONIMO-3425:
-----------------------------------------
reorganized the directory structures on the website as well as added symbolic links to match the schema names with the actual target name space.
OpenEJB related schemas have not been updated.
> 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.