You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Jarek Gawor (JIRA)" <ji...@apache.org> on 2007/06/01 21:48:18 UTC
[jira] Created: (GERONIMO-3204) EJB deployment processing issue
with Geronimo plan
EJB deployment processing issue with Geronimo plan
--------------------------------------------------
Key: GERONIMO-3204
URL: https://issues.apache.org/jira/browse/GERONIMO-3204
Project: Geronimo
Issue Type: Bug
Security Level: public (Regular issues)
Reporter: Jarek Gawor
Discussion from the list:
Recently the GERONIMO-348 patch was committed. That is causing
problems with EJB deployments. Here's an example.
ejb-xml.jar has 2 ejbs, and one of the ejbs has a service-ref entry:
<enterprise-beans>
<session>
<service-ref></service-ref>
</session>
<session>
</session>
</enterprise-beans>
The G plan has corresponding entries for the beans and one service-ref
overwrite.
Now, during deployment and in case of ejbs the
moduleBuilder.buildNaming() function is called once per each bean. The
specDD parameter will point only the given bean's xml data but the
planDD parameter will always point to the entire G plan. That means
when buildNaming() is called for the second bean and even though it
has no service-refs, one service-ref overwrite will be discovered in
the G plan. And with the GERONIMO-348 patch the deployment will fail.
So it seems like the ejb deployment processing needs to change to pass
only the relevant parts of the particular ejb as the planDD.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3204) EJB deployment processing issue
with Geronimo plan
Posted by "Jarek Gawor (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12500829 ]
Jarek Gawor commented on GERONIMO-3204:
---------------------------------------
It's not. The log.warn() fix was a workaround for the larger ejb deployment issue. This bug was open to fix that ejb deployment issue.
> EJB deployment processing issue with Geronimo plan
> --------------------------------------------------
>
> Key: GERONIMO-3204
> URL: https://issues.apache.org/jira/browse/GERONIMO-3204
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Reporter: Jarek Gawor
>
> Discussion from the list:
> Recently the GERONIMO-348 patch was committed. That is causing
> problems with EJB deployments. Here's an example.
> ejb-xml.jar has 2 ejbs, and one of the ejbs has a service-ref entry:
> <enterprise-beans>
> <session>
> <service-ref></service-ref>
> </session>
> <session>
> </session>
> </enterprise-beans>
> The G plan has corresponding entries for the beans and one service-ref
> overwrite.
> Now, during deployment and in case of ejbs the
> moduleBuilder.buildNaming() function is called once per each bean. The
> specDD parameter will point only the given bean's xml data but the
> planDD parameter will always point to the entire G plan. That means
> when buildNaming() is called for the second bean and even though it
> has no service-refs, one service-ref overwrite will be discovered in
> the G plan. And with the GERONIMO-348 patch the deployment will fail.
> So it seems like the ejb deployment processing needs to change to pass
> only the relevant parts of the particular ejb as the planDD.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3204) EJB deployment processing issue
with Geronimo plan
Posted by "Donald Woods (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12500827 ]
Donald Woods commented on GERONIMO-3204:
----------------------------------------
Not sure how GERONIMO-348 is causing problems, given the original throw() code in the patch was changed to log.warn() in Rev539548 - http://svn.apache.org/viewcvs?view=rev&rev=539548
> EJB deployment processing issue with Geronimo plan
> --------------------------------------------------
>
> Key: GERONIMO-3204
> URL: https://issues.apache.org/jira/browse/GERONIMO-3204
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Reporter: Jarek Gawor
>
> Discussion from the list:
> Recently the GERONIMO-348 patch was committed. That is causing
> problems with EJB deployments. Here's an example.
> ejb-xml.jar has 2 ejbs, and one of the ejbs has a service-ref entry:
> <enterprise-beans>
> <session>
> <service-ref></service-ref>
> </session>
> <session>
> </session>
> </enterprise-beans>
> The G plan has corresponding entries for the beans and one service-ref
> overwrite.
> Now, during deployment and in case of ejbs the
> moduleBuilder.buildNaming() function is called once per each bean. The
> specDD parameter will point only the given bean's xml data but the
> planDD parameter will always point to the entire G plan. That means
> when buildNaming() is called for the second bean and even though it
> has no service-refs, one service-ref overwrite will be discovered in
> the G plan. And with the GERONIMO-348 patch the deployment will fail.
> So it seems like the ejb deployment processing needs to change to pass
> only the relevant parts of the particular ejb as the planDD.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.