Hi, I was looking in to the $subject for last couple of days. Right now transaction manager is tightly couples to the servlet container (tomcat). Atomikos get initialized through a tomcat listener. And the Transaction Factory get initialized by the tomcat itself. After that within the dataservices-core we get the UserTransaction manager via a JNDI lookup.
The complication is, the JNDI does not work in OSGi environment at the moment. (Note that it is working for web-apps). The reason is, JNDI try to resolve the context through context classLoader. If the context classLoader is web-app ClassLoader it is working. But if the context classLoader is bundle/context-finder it is not working. OSGi enterprise spec has a separate section for JNDI. There they are using a service based model to overcome the above problems. While searching for the reading materials i came across, OSGi JTA spec as well. Apache aries[1] has a OSGi JNDI + JTA modules. [1] http://aries.apache.org/downloads/currentrelease.html -- Pradeep Fernando Software Engineer Member, Management Committee - Platform & Cloud Technologies WSO2 Inc; http://wso2.com/ blog: http://pradeepfernando.blogspot.com/ m: +94776603662
_______________________________________________ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
