Hi All, According to the call we had with Atomikos team we tryout their new transaction-osgi bundle (version 3.8.0.M1). Earlier transaction-manager was tightly couple with Tomcat. By using new Atomikos OSGi bundle we could able to successfully get rid of Tomcat extensions used for transaction manager integration. Here what we did,
1. created a orbit bundle. - We cannot directly used transaction-osgi bundle which they have provided because @ the runtime it looks for javax.transaction package. But the version it looks for and version we having is different. 2. created transaction manager component/feature. This component do the following tasks. a. Using Declarative Service access, get the TransactionManager service & UserTransaction service. b. Then register those TransactionManager & UserTransaction into JNDI. So it's no matter whether OSGi aware app or not, anyone can access transaction manager by doing a JNDI lookup. When registering TransactionManager & UserTransaction into JNDI, we just create a new InitialContext and bind to it. We tested this by installing transaction-manager feature into DSS and it works fine. But we are not sure whether this is the best way to register with JNDI because the OSGi recommended way to bind InitialContext is different as describes in http://www.infoq.com/news/2010/03/osgi-enterprise-42-released. Pradeep/Sameera does anyone of you know the best way to do this or the way we did is OK ? Regards, Dinusha.
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
