[jira] Updated: (GERONIMO-348) Invalid module path or references in plan should result in failed deployment or warning

["Matt Hogstrom (JIRA)" <de...@geronimo.apache.org>]

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

Matt Hogstrom updated GERONIMO-348:
-----------------------------------

    Fix Version: 1.1
                     (was: 1.0)

Moving to 1.1 for a resolution.  Given the time to get 1.0 out I don't think this is on the critical path.

> Invalid module path or references in plan should result in failed deployment or warning
> ---------------------------------------------------------------------------------------
>
>          Key: GERONIMO-348
>          URL: http://issues.apache.org/jira/browse/GERONIMO-348
>      Project: Geronimo
>         Type: Bug
>   Components: deployment
>     Reporter: Jeremy Boynes
>     Assignee: Aaron Mulder
>      Fix For: 1.1

>
> If an EAR deployment plan contains a entry for a module but the path does not match that of a module in the application.xml then an error or warning should be issued at deployment time.
> A likely reason for this is that a developer copied the plan from another but forgot to change the uri entry for the submodule; or it could just be a simple typo. In either way, the plan won't match the intended module from the application.xml resulting in erroroneous behaviour.
> (added)
> In addition, elements in a plan that do not correspond to elements in the deployment descriptor should result in a warning or error.  Examples would be an ejb listed in the openejb plan that does not correspond to an ejb in the ejb-jar.xml, or a resource-ref in the ejb that does not correspond to a resource-ref in the ejb-jar.xml.

-- 
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