Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Message-ID: <9819341.1179331156324.JavaMail.jira@brutus>
Date: Wed, 16 May 2007 08:59:16 -0700 (PDT)
From: "Donald Woods (JIRA)" <jira@apache.org>
To: dev@geronimo.apache.org
Subject: [jira] Updated: (GERONIMO-348) Invalid module path or references in
 plan should result in failed deployment or warning
In-Reply-To: <1545032378.1096740512133.JavaMail.apache@nagoya>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

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

    Affects Version/s: 2.0-M6
                       1.x
        Fix Version/s:     (was: 2.0-M5)
                       2.0-M6
             Assignee: Donald Woods

> 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: Donald Woods
>            Priority: Critical
>             Fix For: 2.0-M6
>
>         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 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.