It looks like it gets registered as a result of a config admin change. In any case if you look in the service registry using the javax.transaction.TransactionManager interface you should be able find it. This is part of the upcoming enterprise osgi specification.
Alasdair On 15 March 2010 16:51, Donald Woods <[email protected]> wrote: > While working on OPENJPA-1524 reported by Tim, I'm trying to figure out > how the Aries TransactionManagerService is being registered in a generic > way so our OpenJPA code will work with any TM service provider. > > In looking at the Aries transaction module, I'm not seeing how it is > being registered in the ServiceRegistry with a common OSGi name that > isn't Aries specific. > > transaction/transaction-manager/target/sources/org/apache/aries/transaction/Activator.java:45 > - > props.put(Constants.SERVICE_PID, getName()); > bundleContext.registerService(ManagedServiceFactory.class.getName(), > this, props); > > where getName() is - > public String getName() { > return "org.apache.aries.transaction"; > } > > Shouldn't the Aries TransactionManagerService also be registered as > "javax.transaction.TransactionManager" or is that being handled outside > of the BundleActivator code? > > > -Donald > -- Alasdair Nottingham [email protected]
