[
https://issues.apache.org/jira/browse/OPENJPA-1593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dick reassigned OPENJPA-1593:
-------------------------------------
Assignee: Michael Dick (was: Donald Woods)
Mailing list post jogged my memory to look at the patch, which looks good.
The only question I have is with the service registration triggered in
PersistenceActivator. It looks benign but it'd be nice to know whether there's
an effect when running with Aries before we commit.
> Create an OSGiManagedRuntime
> ----------------------------
>
> Key: OPENJPA-1593
> URL: https://issues.apache.org/jira/browse/OPENJPA-1593
> Project: OpenJPA
> Issue Type: Sub-task
> Components: osgi
> Affects Versions: 2.0.0-beta
> Reporter: Donald Woods
> Assignee: Michael Dick
> Fix For: 2.2.0
>
> Attachments: OPENJPA-1593-1.patch, OPENJPA-1593-2.patch,
> OPENJPA-1593-3.patch, OPENJPA-1593-4.patch
>
>
> Follow-on to OPENJPA-1524 to create a generic OSGiManagedRuntime class that
> would work for vendors/frameworks other than Apache Aries.
> Tim's original suggestion was - One implementation suggestion would be to use
> a ServiceTracker to keep track of the JTA services. This would allow for lazy
> lookup and also provide a notification if the service is unregistered.
> This should then be possible to implement as a relatively simple subclass of
> RegistryManagedRuntime that overrides getTransactionManager(). I don't know
> if you have a nice mechanism to pass a BundleContext yet, but I don't think
> that should pose a significant problem.
> Now that we have a BundleUtils.java to require OSGi classes in our runtime,
> we should be able to lookup
> "javax.transaction.TransactionSynchronizationRegistry" from the
> ServiceRegistry to use, instead of relying on the current JNDI lookup which
> is Aries specific.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
