geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Quintin Beukes (JIRA)" <>
Subject [jira] Updated: (GERONIMO-4928) In the JPA persistence.xml loading code, exclude-unlisted-classes handling not compliant with JPA3.0 spec
Date Fri, 23 Oct 2009 20:53:59 GMT


Quintin Beukes updated GERONIMO-4928:

    Attachment: external-jpa-entity-reference.patch

Changes the handling of exclude-unlisted-classes

> In the JPA persistence.xml loading code, exclude-unlisted-classes handling not compliant
with JPA3.0 spec
> ---------------------------------------------------------------------------------------------------------
>                 Key: GERONIMO-4928
>                 URL:
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: deployment, persistence
>    Affects Versions: 2.1.4
>            Reporter: Quintin Beukes
>             Fix For: 2.1.4, 2.2, 3.0
>         Attachments: external-jpa-entity-reference.patch
> According to the final release of the EJB 3.0 JPA spec, section
> The set of managed persistence classes that are managed by a persistence unit is defined
by using one or
> more of the following:[41]
>      • One or more object/relational mapping XML files
>      • One or more jar files that will be searched for classes
>      • An explicit list of the classes
>      • The annotated managed persistence classes contained in the root of the persistence
unit (unless
>          the exclude-unlisted-classes element is specified)
> ... further on...
> All classes must be on the classpath to ensure that entity managers from different persistence
units that
> map the same class will be accessing the same identical class.
> This says that if exclude-unlisted-classes is specified as true, then only the classes
listed in <class> elements must be used in the PU. If it is specified as false, then
the annotated classes must be included. It's the only thing that exclude-unlisted-classes
affects. It doesn't affect classes from other units, and if false it doesn't say that <class>
must be ignored, which is what the following code does in
>         if (excludeUnlistedClasses) {
>             gbeanData.clearAttribute("jarFileUrls");
>         } else {
>             gbeanData.clearAttribute("managedClassNames");
>         }
> I removed the else block to leave:
>         if (excludeUnlistedClasses) {
>             gbeanData.clearAttribute("jarFileUrls");
>         }
> Without this Geronimo isn't JavaEE 5 compliant.

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

View raw message