[GERONIMO-348] Invalid module path or references in plan should result in failed deployment or warning

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 1.x, 2.0-M6
• Fix Version/s: 2.0-M6
• Component/s: deployment
• Patch Info: Patch Available
• Assignee: Rakesh Midha
• Reporter: Jeremy Boynes
• Created: 02/Oct/04 18:08
• Updated: 18/May/07 18:32
• Resolved: 16/May/07 18:02

Description

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.

Issue Links

• is cloned by: GERONIMO-2665 CLONE -Invalid module path or references in plan should result in failed deployment or warning
• is duplicated by: OPENEJB-407 Invalid ejb/local references in plan should result in failed deployment or warning