[
https://issues.apache.org/jira/browse/ARIES-1018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christoph Gritschenberger updated ARIES-1018:
---------------------------------------------
Attachment: fix-exception.patch
> JPA container throws Exception when stopped without a JPA-Provider present
> --------------------------------------------------------------------------
>
> Key: ARIES-1018
> URL: https://issues.apache.org/jira/browse/ARIES-1018
> Project: Aries
> Issue Type: Bug
> Components: JPA
> Environment: karaf 3.0.0-SNAPSHOT, KARAF-2.3.1-SHAPSHOT
> Reporter: Christoph Gritschenberger
> Attachments: fix-exception.patch
>
>
> To reproduce unpack the latest karaf-snapshot and install the JPA-feature:
> {code}
> feature:install jpa
> {code}
> and install a bundle containing a persistence-unit.
> stop the JPA Container bundle.
> {code}
> {code}
> This happens since aries-util was upgraded to 1.1.0. The issue did not occur
> with util-1.0.0.
> I investigated a bit and found the problem:
> In util-1.1.0 the BundleHookBundleTracker was changed to untrack all bundles
> when it's closed. In util-1.0 closing did essentially nothing but setting a
> closed-flag.
> So when using JPA Container with util-1.1.0 the persistence-units are
> destroyed without ever being created.
> This also happens when having a JPA Provider (like OpenJPA) installed, but
> when it's stopped before the the JPA-Container Bundle is stopped (the usual
> case).
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
