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 2013/06/26 13:33:20 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: PersistenceBundleHelper.java
Here's a fixed version of the file that relies solely on BundleWiring. I guess a proper approach would be to fallback to the current behaviour when running without BundleWiring support. It also only utilizes only the first found match as did the previous implementation
> 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
>
>
> 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)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira