aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Ward (JIRA)" <>
Subject [jira] Resolved: (ARIES-455) Allow the Aries JPA runtime to process WAB files
Date Wed, 15 Dec 2010 09:07:01 GMT


Timothy Ward resolved ARIES-455.

    Resolution: Fixed

> Allow the Aries JPA runtime to process WAB files
> ------------------------------------------------
>                 Key: ARIES-455
>                 URL:
>             Project: Aries
>          Issue Type: Improvement
>          Components: JPA
>    Affects Versions: 0.3
>            Reporter: Timothy Ward
>            Assignee: Timothy Ward
>             Fix For: 0.3
> The Aries JPA runtime currently deliberately ignores WAB files because it isn't clear
whether they should be processed according to Java EE rules or not.
> I propose the following:
> * A WAB with a Meta-Persistence header should be treated like any other persistence bundle
> * A WAB with no Meta-Persistence header should follow the rules of the OSGi Web Applications
specification. Namely the JPA runtime should look for META-INF/persistence.xml in any locations
listed on the bundle classpath (or in the root if no classpath is defined).
> This is not the normal Java EE behaviour. We will not find META-INF/persistence.xml in
any jar in WEB-INF/lib, or in WEB-INF/classes unless it is explicitly on the bundle classpath.
This is, however, consistent with normal WAB behaviour and I believe is therefore the correct

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

View raw message