Uploaded image for project: 'Geronimo'
  1. Geronimo
  2. GERONIMO-3204

EJB deployment processing issue with Geronimo plan

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Open
    • Major
    • Resolution: Unresolved
    • None
    • None
    • None
    • Security Level: public (Regular issues)
    • None

    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.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              gawor@mcs.anl.gov Jarek Gawor
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated: