You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tomee.apache.org by "David Blevins (JIRA)" <ji...@apache.org> on 2007/08/13 22:09:31 UTC
[jira] Closed: (OPENEJB-407) Invalid ejb/local references in plan
should result in failed deployment or warning
[ https://issues.apache.org/jira/browse/OPENEJB-407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Blevins closed OPENEJB-407.
---------------------------------
Resolution: Fixed
Doesn't look like there will be any more releases from the 2.x codebase.
> Invalid ejb/local references in plan should result in failed deployment or warning
> ----------------------------------------------------------------------------------
>
> Key: OPENEJB-407
> URL: https://issues.apache.org/jira/browse/OPENEJB-407
> Project: OpenEJB
> Issue Type: Bug
> Components: deployment
> Affects Versions: 2.3
> Environment: Any
> Reporter: Rakesh Midha
> Attachments: noref407.patch
>
>
> This is a part of issue http://issues.apache.org/jira/browse/GERONIMO-348 in Geronimo Tree.
> 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.
> 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.
-
You can reply to this email to add a comment to the issue online.