You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by de...@geronimo.apache.org on 2004/10/02 20:08:32 UTC
[jira] Created: (GERONIMO-348) Invalid module path in plan should result in failed deployment
Message:
A new issue has been created in JIRA.
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/GERONIMO-348
Here is an overview of the issue:
---------------------------------------------------------------------
Key: GERONIMO-348
Summary: Invalid module path in plan should result in failed deployment
Type: Bug
Status: Unassigned
Priority: Major
Project: Apache Geronimo
Assignee:
Reporter: Jeremy Boynes
Created: Sat, 2 Oct 2004 11:08 AM
Updated: Sat, 2 Oct 2004 11:08 AM
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 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.
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-348) Invalid module path in plan should result in failed deployment
Posted by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org>.
[ http://nagoya.apache.org/jira/browse/GERONIMO-348?page=history ]
Aaron Mulder updated GERONIMO-348:
----------------------------------
Component: deployment
> Invalid module path in plan should result in failed deployment
> --------------------------------------------------------------
>
> Key: GERONIMO-348
> URL: http://nagoya.apache.org/jira/browse/GERONIMO-348
> Project: Apache Geronimo
> Type: Bug
> Components: deployment
> Reporter: Jeremy Boynes
>
> 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 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Assigned: (GERONIMO-348) Invalid module path or references
in plan should result in failed deployment or warning
Posted by "Rakesh Midha (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-348?page=all ]
Rakesh Midha reassigned GERONIMO-348:
-------------------------------------
Assignee: Rakesh Midha
> Invalid module path or references in plan should result in failed deployment or warning
> ---------------------------------------------------------------------------------------
>
> Key: GERONIMO-348
> URL: http://issues.apache.org/jira/browse/GERONIMO-348
> Project: Geronimo
> Issue Type: Bug
> Components: deployment
> Reporter: Jeremy Boynes
> Assigned To: 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
[jira] Updated: (GERONIMO-348) Invalid module path or references in
plan should result in failed deployment or warning
Posted by "Rakesh Midha (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-348?page=all ]
Rakesh Midha updated GERONIMO-348:
----------------------------------
Patch Info: [Patch Available]
Fix Version/s: 2.0
(was: Wish List)
Assignee: (was: Rakesh Midha)
Marking Patch available, making unassigned so tat someone can review and commit.
thanks
> Invalid module path or references in plan should result in failed deployment or warning
> ---------------------------------------------------------------------------------------
>
> Key: GERONIMO-348
> URL: http://issues.apache.org/jira/browse/GERONIMO-348
> Project: Geronimo
> Issue Type: Bug
> Components: deployment
> Reporter: Jeremy Boynes
> Priority: Critical
> Fix For: 2.0
>
> 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.
-
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
[jira] Updated: (GERONIMO-348) Invalid module path or references in
plan should result in failed deployment or warning
Posted by "Donald Woods (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (GERONIMO-348) Invalid module path or references in plan should result in failed deployment or warning
Posted by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-348?page=all ]
Aaron Mulder updated GERONIMO-348:
----------------------------------
Fix Version: 1.0-M5
> Invalid module path or references in plan should result in failed deployment or warning
> ---------------------------------------------------------------------------------------
>
> Key: GERONIMO-348
> URL: http://issues.apache.org/jira/browse/GERONIMO-348
> Project: Geronimo
> Type: Bug
> Components: deployment
> Reporter: Jeremy Boynes
> Assignee: Aaron Mulder
> Fix For: 1.0-M5
>
> 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
[jira] Assigned: (GERONIMO-348) Invalid module path or references in plan should result in failed deployment or warning
Posted by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-348?page=all ]
Aaron Mulder reassigned GERONIMO-348:
-------------------------------------
Assign To: Aaron Mulder
> Invalid module path or references in plan should result in failed deployment or warning
> ---------------------------------------------------------------------------------------
>
> Key: GERONIMO-348
> URL: http://issues.apache.org/jira/browse/GERONIMO-348
> Project: Geronimo
> Type: Bug
> Components: deployment
> Reporter: Jeremy Boynes
> Assignee: Aaron Mulder
>
> 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
[jira] Updated: (GERONIMO-348) Invalid module path or references in
plan should result in failed deployment or warning
Posted by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-348?page=all ]
Aaron Mulder updated GERONIMO-348:
----------------------------------
Assign To: (was: Aaron Mulder)
> Invalid module path or references in plan should result in failed deployment or warning
> ---------------------------------------------------------------------------------------
>
> Key: GERONIMO-348
> URL: http://issues.apache.org/jira/browse/GERONIMO-348
> Project: Geronimo
> Type: Bug
> Components: deployment
> Reporter: Jeremy Boynes
> Priority: Critical
> Fix For: 1.2
>
> 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
[jira] Commented: (GERONIMO-348) Invalid module path or references in plan should result in failed deployment or warning
Posted by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-348?page=comments#action_12315811 ]
Aaron Mulder commented on GERONIMO-348:
---------------------------------------
Fixed for EAR with bogus modules and EJB JAR with bogus EJBs
Still need to look at EJB Refs, Resource Refs, Env Entries, Web Services Refs.
For other problems of this nature, please file separate bugs.
> Invalid module path or references in plan should result in failed deployment or warning
> ---------------------------------------------------------------------------------------
>
> Key: GERONIMO-348
> URL: http://issues.apache.org/jira/browse/GERONIMO-348
> Project: Geronimo
> Type: Bug
> Components: deployment
> Reporter: Jeremy Boynes
> Assignee: Aaron Mulder
>
> 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
[jira] Updated: (GERONIMO-348) Invalid module path or references in
plan should result in failed deployment or warning
Posted by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-348?page=all ]
Aaron Mulder updated GERONIMO-348:
----------------------------------
Fix Version: 1.1
(was: 1.2)
Priority: Critical (was: Major)
The validation required is pretty simple, and we get a lot of users having problems with Resource/EJB references; I'd like this on the list for 1.1
> Invalid module path or references in plan should result in failed deployment or warning
> ---------------------------------------------------------------------------------------
>
> Key: GERONIMO-348
> URL: http://issues.apache.org/jira/browse/GERONIMO-348
> Project: Geronimo
> Type: Bug
> Components: deployment
> Reporter: Jeremy Boynes
> Assignee: Aaron Mulder
> Priority: Critical
> Fix For: 1.1
>
> 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
[jira] Updated: (GERONIMO-348) Invalid module path or references in
plan should result in failed deployment or warning
Posted by "Donald Woods (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (GERONIMO-348) Invalid module path or references in plan should result in failed deployment or warning
Posted by "David Jencks (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-348?page=all ]
David Jencks updated GERONIMO-348:
----------------------------------
Summary: Invalid module path or references in plan should result in failed deployment or warning (was: Invalid module path in plan should result in failed deployment)
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.
was:
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 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.
Environment:
> Invalid module path or references in plan should result in failed deployment or warning
> ---------------------------------------------------------------------------------------
>
> Key: GERONIMO-348
> URL: http://issues.apache.org/jira/browse/GERONIMO-348
> Project: Geronimo
> Type: Bug
> Components: deployment
> Reporter: Jeremy Boynes
>
> 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
[jira] Updated: (GERONIMO-348) Invalid module path or references in
plan should result in failed deployment or warning
Posted by "Matt Hogstrom (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-348?page=all ]
Matt Hogstrom updated GERONIMO-348:
-----------------------------------
Fix Version/s: Wish List
(was: 1.2)
Moving out for consideration for 2.0
> Invalid module path or references in plan should result in failed deployment or warning
> ---------------------------------------------------------------------------------------
>
> Key: GERONIMO-348
> URL: http://issues.apache.org/jira/browse/GERONIMO-348
> Project: Geronimo
> Issue Type: Bug
> Components: deployment
> Reporter: Jeremy Boynes
> 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
[jira] Resolved: (GERONIMO-348) Invalid module path or references
in plan should result in failed deployment or warning
Posted by "Donald Woods (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Donald Woods resolved GERONIMO-348.
-----------------------------------
Resolution: Fixed
Updated patch applied.
Committed revision 538671 in trunk.
Verified build worked with itests and Servlet-Examples could be deployed and accessed..
> 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: 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.
[jira] Updated: (GERONIMO-348) Invalid module path or references in plan should result in failed deployment or warning
Posted by "David Blevins (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-348?page=all ]
David Blevins updated GERONIMO-348:
-----------------------------------
Fix Version: 1.0
(was: 1.0-M5)
> Invalid module path or references in plan should result in failed deployment or warning
> ---------------------------------------------------------------------------------------
>
> Key: GERONIMO-348
> URL: http://issues.apache.org/jira/browse/GERONIMO-348
> Project: Geronimo
> Type: Bug
> Components: deployment
> Reporter: Jeremy Boynes
> Assignee: Aaron Mulder
> Fix For: 1.0
>
> 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
[jira] Updated: (GERONIMO-348) Invalid module path or references in
plan should result in failed deployment or warning
Posted by "Matt Hogstrom (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-348?page=all ]
Matt Hogstrom updated GERONIMO-348:
-----------------------------------
Fix Version: 1.2
(was: 1.1)
> Invalid module path or references in plan should result in failed deployment or warning
> ---------------------------------------------------------------------------------------
>
> Key: GERONIMO-348
> URL: http://issues.apache.org/jira/browse/GERONIMO-348
> Project: Geronimo
> Type: Bug
> Components: deployment
> Reporter: Jeremy Boynes
> Assignee: Aaron Mulder
> Priority: Critical
> Fix For: 1.2
>
> 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
[jira] Updated: (GERONIMO-348) Invalid module path or references in plan should result in failed deployment or warning
Posted by "Matt Hogstrom (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-348?page=all ]
Matt Hogstrom updated GERONIMO-348:
-----------------------------------
Fix Version: 1.1
(was: 1.0)
Moving to 1.1 for a resolution. Given the time to get 1.0 out I don't think this is on the critical path.
> Invalid module path or references in plan should result in failed deployment or warning
> ---------------------------------------------------------------------------------------
>
> Key: GERONIMO-348
> URL: http://issues.apache.org/jira/browse/GERONIMO-348
> Project: Geronimo
> Type: Bug
> Components: deployment
> Reporter: Jeremy Boynes
> Assignee: Aaron Mulder
> Fix For: 1.1
>
> 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
[jira] Updated: (GERONIMO-348) Invalid module path or references in
plan should result in failed deployment or warning
Posted by "Donald Woods (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Donald Woods updated GERONIMO-348:
----------------------------------
Attachment: G348.patch
Updated patch, which was created against Rev538622.
Included the same refMap updates to JAXWSServiceRefBuilder.java and SwitchingServiceRefBuilder.java.
> 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: 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.
[jira] Updated: (GERONIMO-348) Invalid module path or references in
plan should result in failed deployment or warning
Posted by "Rakesh Midha (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-348?page=all ]
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 http://issues.apache.org/jira/browse/OPENEJB-407 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: http://issues.apache.org/jira/browse/GERONIMO-348
> 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 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