Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Message-ID: <21532485.1182881126741.JavaMail.jira@brutus>
Date: Tue, 26 Jun 2007 11:05:26 -0700 (PDT)
From: "David Jencks (JIRA)" <jira@apache.org>
To: dev@geronimo.apache.org
Subject: [jira] Created: (GERONIMO-3263) PersistenceUnitBuilder is sometimes
 putting the PersistenceUnitGBean in the wrong configuration
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

PersistenceUnitBuilder is sometimes putting the PersistenceUnitGBean in the wrong configuration
-----------------------------------------------------------------------------------------------

                 Key: GERONIMO-3263
                 URL: https://issues.apache.org/jira/browse/GERONIMO-3263
             Project: Geronimo
          Issue Type: Bug
      Security Level: public (Regular issues)
          Components: persistence
    Affects Versions: 2.0-M6
            Reporter: David Jencks
            Assignee: David Jencks
             Fix For: 2.0-M7


PersistenceUnitBuilder is always putting PersistenceUnitGBeans in the root ear context, which won't work if the PU is actually in a war.  I think I did this because of a problem with wars finding persistence units in ear libs or other shared locations.  It's possible that fixing this problem will uncover another problem if  a war and an ejb module both include a jar with a PU in their manifest classpath.  The potential problem would be that the war gets the PUGBean and the ejb module can't find it.  I believe the spec warns against doing this.  In any case I believe the solution should this problem arise would be to deploy PUGBeans in both the war and ejb module: results from a program using both are likely to be really screwy, but as the spec says "DONT DO THAT".

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.