geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Donald Woods (JIRA)" <>
Subject [jira] Commented: (GERONIMO-3204) EJB deployment processing issue with Geronimo plan
Date Fri, 01 Jun 2007 20:00:53 GMT


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 -

> EJB deployment processing issue with Geronimo plan
> --------------------------------------------------
>                 Key: GERONIMO-3204
>                 URL:
>             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.

View raw message