You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Alan Cabrera (JIRA)" <de...@geronimo.apache.org> on 2006/07/16 09:06:28 UTC

[jira] Updated: (GERONIMO-1642) Deployment plan namespace validation

     [ http://issues.apache.org/jira/browse/GERONIMO-1642?page=all ]

Alan Cabrera updated GERONIMO-1642:
-----------------------------------

    Fix Version/s: 1.1.x
                       (was: 1.1.1)

Moving unassigned issues over to the 1.1.x pool where they can be worked on for the, in all probability, 1.1.2 patch.

> Deployment plan namespace validation
> ------------------------------------
>
>                 Key: GERONIMO-1642
>                 URL: http://issues.apache.org/jira/browse/GERONIMO-1642
>             Project: Geronimo
>          Issue Type: Improvement
>      Security Level: public(Regular issues) 
>          Components: web, deployment, OpenEJB
>    Affects Versions: 1.1
>            Reporter: Aaron Mulder
>            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: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira