geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rakesh Midha (JIRA)" <j...@apache.org>
Subject [jira] Updated: (GERONIMO-2665) CLONE -Invalid module path or references in plan should result in failed deployment or warning
Date Fri, 15 Dec 2006 11:01:23 GMT
     [ http://issues.apache.org/jira/browse/GERONIMO-2665?page=all ]

Rakesh Midha updated GERONIMO-2665:
-----------------------------------

    Assignee:     (was: Rakesh Midha)



Can you please close this issue, i wanted to create a clone of this JIRA in OpenEJB, but I
didnt knew  that I have to do it manually, as cloning of this issue will create new issue
in Geronimo project only.

My mistake. Can someone please close it for me.

Thanks in advance
Rakesh

> CLONE -Invalid module path or references in plan should result in failed deployment or
warning
> ----------------------------------------------------------------------------------------------
>
>                 Key: GERONIMO-2665
>                 URL: http://issues.apache.org/jira/browse/GERONIMO-2665
>             Project: Geronimo
>          Issue Type: Bug
>          Components: deployment
>            Reporter: Rakesh Midha
>            Priority: Critical
>             Fix For: Wish List
>
>
> 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

        

Mime
View raw message