Return-Path: 
 <dev-return-50624-apmail-geronimo-dev-archive=geronimo.apache.org@geronimo.apache.org>
Delivered-To: apmail-geronimo-dev-archive@www.apache.org
Received: (qmail 16725 invoked from network); 1 Jun 2007 19:48:46 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 1 Jun 2007 19:48:45 -0000
Received: (qmail 77148 invoked by uid 500); 1 Jun 2007 19:48:44 -0000
Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org
Received: (qmail 77066 invoked by uid 500); 1 Jun 2007 19:48:44 -0000
Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:dev-help@geronimo.apache.org>
list-unsubscribe: <mailto:dev-unsubscribe@geronimo.apache.org>
List-Post: <mailto:dev@geronimo.apache.org>
Reply-To: dev@geronimo.apache.org
List-Id: <dev.geronimo.apache.org>
Delivered-To: mailing list dev@geronimo.apache.org
Received: (qmail 77042 invoked by uid 99); 1 Jun 2007 19:48:44 -0000
Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 01 Jun 2007 12:48:44 -0700
X-ASF-Spam-Status: No, hits=-100.0 required=10.0
	tests=ALL_TRUSTED
X-Spam-Check-By: apache.org
Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 01 Jun 2007 12:48:38 -0700
Received: from brutus (localhost [127.0.0.1])
	by brutus.apache.org (Postfix) with ESMTP id 9933E71418E
	for <dev@geronimo.apache.org>; Fri,  1 Jun 2007 12:48:18 -0700 (PDT)
Message-ID: <29071930.1180727298625.JavaMail.jira@brutus>
Date: Fri, 1 Jun 2007 12:48:18 -0700 (PDT)
From: "Jarek Gawor (JIRA)" <jira@apache.org>
To: dev@geronimo.apache.org
Subject: [jira] Created: (GERONIMO-3204) EJB deployment processing issue
 with Geronimo plan
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-Virus-Checked: Checked by ClamAV on apache.org

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.