geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rakesh Midha (JIRA)" <>
Subject [jira] Updated: (GERONIMO-348) Invalid module path or references in plan should result in failed deployment or warning
Date Fri, 15 Dec 2006 11:23:23 GMT
     [ ]

Rakesh Midha updated GERONIMO-348:

    Attachment: noref348.patch

Added code to check if plan contains refrences which are not defined in deployment descriptors.

Now we get deployment failure if plan contains 
                        Resource Refs
                        Web Services Refs
                        Admin Object refs
missing in deployment descriptor.

Also created new Jira in OpenEJB to check
same for
                       EJB Remote refs
                       EJB Local refs

Seperate patch provided in openejb-407 for fixing openejb part.

> Invalid module path or references in plan should result in failed deployment or warning
> ---------------------------------------------------------------------------------------
>                 Key: GERONIMO-348
>                 URL:
>             Project: Geronimo
>          Issue Type: Bug
>          Components: deployment
>            Reporter: Jeremy Boynes
>         Assigned To: Rakesh Midha
>            Priority: Critical
>             Fix For: Wish List
>         Attachments: noref348.patch
> 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
> 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
> (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:
For more information on JIRA, see:


View raw message