You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by "Tuomas Kiviaho (JIRA)" <ji...@apache.org> on 2015/01/16 09:05:34 UTC

[jira] [Updated] (ARIES-964) Support for bundle fragments

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

Tuomas Kiviaho updated ARIES-964:
---------------------------------
    Attachment: PersistenceBundleManager.java

Updated against r1637878

> Support for bundle fragments
> ----------------------------
>
>                 Key: ARIES-964
>                 URL: https://issues.apache.org/jira/browse/ARIES-964
>             Project: Aries
>          Issue Type: New Feature
>          Components: JPA
>            Reporter: Tuomas Kiviaho
>         Attachments: PersistenceBundleHelper.java, PersistenceBundleHelper.java, PersistenceBundleManager.java, PersistenceBundleManager.patch
>
>
> Currently it's possible to have both persistence.xml and Meta-Persistence: attribute declared on fragment bundle, but it's not very practical because PersistenceUnitInfo#getClassLoader() will return null causing providers to fall apart and there won't be any emf's available because the bundle stays at RESOLVED state.
> I tried to circumvent this by declaring Meta-Persistence: at fragment's host, but required a bit modification to PersistenceBundleHelper#findPersistenceXmlFiles to use BundleWiring#findEntries (when it's available)
> Update:
> Although ACTIVE state is now considered instead of resolved state, this issue is still valid for (multiple) fragment support.
> Patches are not that out-of-date, but I'd gladly send repatches if so deemed.



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