You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@deltaspike.apache.org by "John D. Ament (JIRA)" <ji...@apache.org> on 2016/06/03 11:19:59 UTC

[jira] [Updated] (DELTASPIKE-406) PersistenceUnits#instance singleton does not work in EAR scenarios

     [ https://issues.apache.org/jira/browse/DELTASPIKE-406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

John D. Ament updated DELTASPIKE-406:
-------------------------------------
    Summary: PersistenceUnits#instance singleton does not work in EAR  scenarios  (was: PersistenceUnits#instance sinngleton does not work in EAR  scenarios)

> PersistenceUnits#instance singleton does not work in EAR  scenarios
> -------------------------------------------------------------------
>
>                 Key: DELTASPIKE-406
>                 URL: https://issues.apache.org/jira/browse/DELTASPIKE-406
>             Project: DeltaSpike
>          Issue Type: Bug
>          Components: JPA-Module
>    Affects Versions: 0.5
>            Reporter: Mark Struberg
>            Assignee: Mark Struberg
>            Priority: Minor
>
> Currently the info regarding the various persistence.xml files on the classpath only gets scanned once and stored in the static PersistenceUnits#instance.
> This does not work in EAR scenarios if one of the persistence.xml is in a webapp or if the deltaspike-data-impl is on any other shared ClassLoader.
> We should at least document this restriction it until it's properly fixed.
> A possible fix would be to have a (weak) Map<ClassLoader, PersistenceInfo> which also looks up the parent ClassLodaer chain.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)