You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Donald Woods (JIRA)" <ji...@apache.org> on 2007/05/16 20:08:16 UTC

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

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

Donald Woods updated GERONIMO-1642:
-----------------------------------

    Fix Version/s:     (was: 2.0-M5)
                   2.0-M6
         Assignee: Donald Woods

> Deployment plan namespace validation
> ------------------------------------
>
>                 Key: GERONIMO-1642
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-1642
>             Project: Geronimo
>          Issue Type: Improvement
>      Security Level: public(Regular issues) 
>          Components: deployment, OpenEJB, web
>    Affects Versions: 1.1
>            Reporter: Aaron Mulder
>         Assigned To: Donald Woods
>            Priority: Critical
>             Fix For: 2.0-M6
>
>         Attachments: namespace1642.patch
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.