[
https://issues.apache.org/jira/browse/OPENJPA-1593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12981792#action_12981792
]
Michael Dick commented on OPENJPA-1593:
---------------------------------------
I don't see a testcase in the attached patches, did it get missed when you ran
svn add?
Adding it to AutomaticManagedRuntime should probably wait for 2.2.0 - not sure
we'll find any takers in the next couple of days that can take it on. If you
have a unit test that manually specifies it we might be able to get that into
2.1.0 though..
> 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: Donald Woods
> Fix For: 2.2.0
>
> Attachments: OPENJPA-1593-1.patch, OPENJPA-1593-2.patch,
> OPENJPA-1593-3.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.
-
You can reply to this email to add a comment to the issue online.
