[
https://issues.apache.org/jira/browse/ARIES-1575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15595340#comment-15595340
]
Christian Schneider commented on ARIES-1575:
--------------------------------------------
I think this fix is not correct. You get the PersistenceProvider using the
persistence bundle on addingService but on removingService we still use the
bundle context of aries jpa container.
Would it make sense to use the bundle context of the persistence bundle already
when creating the PersistenceProviderTracker?
> Aries JPA should use the persistence bundle's context to obtain the
> Persistence Provider service
> ------------------------------------------------------------------------------------------------
>
> Key: ARIES-1575
> URL: https://issues.apache.org/jira/browse/ARIES-1575
> Project: Aries
> Issue Type: Bug
> Components: JPA
> Affects Versions: jpa-2.4.0
> Reporter: Timothy Ward
> Fix For: jpa-2.5.0
>
>
> Some JPA implementations (Hibernate) register a service factory for their
> Persistence Provider and cache bundle-level data in the service.
> Aries JPA always uses its own Bundle Context to do the service "get" which
> confuses Hibernate into doing the wrong thing. This causes problems such as:
> https://hibernate.atlassian.net/browse/HHH-10855
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
