geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Donald Woods (JIRA)" <j...@apache.org>
Subject [jira] Updated: (GERONIMO-348) Invalid module path or references in plan should result in failed deployment or warning
Date Fri, 18 May 2007 18:33:16 GMT

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

Donald Woods updated GERONIMO-348:
----------------------------------

    Assignee: Rakesh Midha  (was: Donald Woods)

Changed throw() to just be a log.warn(), due to problems discovered during TCK.
Committed revision 539548 in trunk.
Rakesh, please reopen this issue if you develop a new patch that doesn't break any TCK tests.


> Invalid module path or references in plan should result in failed deployment or warning
> ---------------------------------------------------------------------------------------
>
>                 Key: GERONIMO-348
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-348
>             Project: Geronimo
>          Issue Type: Bug
>          Components: deployment
>    Affects Versions: 1.x, 2.0-M6
>            Reporter: Jeremy Boynes
>         Assigned To: Rakesh Midha
>            Priority: Critical
>             Fix For: 2.0-M6
>
>         Attachments: G348.patch, 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
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.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message