openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Wolfgang Glas (JIRA)" <>
Subject [jira] Commented: (OPENJPA-1593) Create an OSGiManagedRuntime
Date Thu, 17 Feb 2011 08:34:25 GMT


Wolfgang Glas commented on OPENJPA-1593:


  Thanks for applying the patch,

    Best regards, Wolfgang

> Create an OSGiManagedRuntime
> ----------------------------
>                 Key: OPENJPA-1593
>                 URL:
>             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,
> 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 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:


View raw message