geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Jencks (JIRA)" <>
Subject [jira] Commented: (GERONIMO-1642) Deployment plan namespace validation
Date Mon, 18 Dec 2006 08:28:21 GMT
    [ ] 
David Jencks commented on GERONIMO-1642:

I'm really not sure this is still a problem.  For instance JettyModuleBuilder AFAICT throws
an exception explaining the xml problem if it finds a geronimo-web or geronimo-jetty.xml file
that it can't interpret.

When looking for examples that fail keep in mind that XmlBeansUtil.parse does a lot of namespace
substitution and many builders have code to upgrade documents valid for earlier versions of
geronimo plan schemas to the latest versions.  So, "wrong namespace" should mean "namespace
we have never used" rather than "not the current namespace"

> Deployment plan namespace validation
> ------------------------------------
>                 Key: GERONIMO-1642
>                 URL:
>             Project: Geronimo
>          Issue Type: Improvement
>      Security Level: public(Regular issues) 
>          Components: deployment, OpenEJB, web
>    Affects Versions: 1.1
>            Reporter: Aaron Mulder
>         Assigned To: Rakesh Midha
>            Priority: Critical
>             Fix For: 1.1.x
> When you deploy with a geronimo deployment plan packaged in the archive, but it has the
wrong namespace, the file is ignored.  If anything, you get a message saying the plan is required,
or that the archive is not a WAR/JAR/etc.  We should have special detection for geronimo-application.xml,
geronimo-ra.xml, geronimo-web.xml, and openejb-jar.xml that notices if the file is present
but has the wrong namespace, and prints a suggestive WARN or ERROR message to the console.
 Probably for the application.xml, web.xml, ra.xml, and ejb-jar.xml too.
> People have asked for help on the mailing list several times recently when they had this
(bad namespace) problem.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message