[GERONIMO-3204] EJB deployment processing issue with Geronimo plan

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Security Level: public (Regular issues)
• Assignee: Unassigned
• Reporter: Jarek Gawor
• Created: 01/Jun/07 19:48
• Updated: 16/Jun/07 02:11

Description

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.

Issue Links

• relates to: GERONIMO-3248 Extraneous WARN messages during deployment of resource-env-refs in EJB jar