geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jarek Gawor (JIRA)" <j...@apache.org>
Subject [jira] Created: (GERONIMO-3204) EJB deployment processing issue with Geronimo plan
Date Fri, 01 Jun 2007 19:48:18 GMT
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.


Mime
View raw message