[
https://issues.apache.org/jira/browse/GERONIMO-1642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods updated GERONIMO-1642:
-----------------------------------
Patch Info: (was: [Patch Available])
Fix Version/s: (was: 2.0-M6)
Wish List
Assignee: Rakesh Midha (was: Donald Woods)
Patch needs to be reworked to not cause a build failure in client-security....
> 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: Rakesh Midha
> Priority: Critical
> Fix For: Wish List
>
> 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.
