-
1. Re: JCA adaptor dependant on the jboss transaction spi.
timfox Sep 1, 2009 7:05 PM (in response to ataylor)The transaction manager certainly shouldn't assume the JBoss TS transaction manager or it will never work in application servers other than JBoss AS.
The RA needs to work outside JBoss AS, it's kind of the point of a RA that it works with any JEE app server.
The RA code should just deal with a standard JTA transaction manager interface.
How that instance is provided to the RA code could be done in the RA config. E.g. specify a class which provides a transaction manager instance.
But any dependencies on JBoss AS or JBoss TS specifics is a big no-no. -
2. Re: JCA adaptor dependant on the jboss transaction spi.
ataylor Sep 3, 2009 5:44 AM (in response to ataylor)Ive added some extra configuration for specifying the class/method to create the tx manager and updated the docs.
Ive also noticed that the JMS bridge uses the same jboss ts API, maybe this should be removed as well? -
3. Re: JCA adaptor dependant on the jboss transaction spi.
timfox Sep 4, 2009 3:19 PM (in response to ataylor)"ataylor" wrote:
Ive also noticed that the JMS bridge uses the same jboss ts API, maybe this should be removed as well?
+1 -
4. Re: JCA adaptor dependant on the jboss transaction spi.
ataylor Sep 9, 2009 4:42 AM (in response to ataylor)Ive made these changes and will check them in. Ive added a couple of helper classes for jboss 4 and 5. Currently we have a jboss-as-security.jar which i was going to rename to jboss-as-integration.jar and add these classes, i think this will be better moving forward as well. I'll commit if no one has any issues with this.
-
5. Re: JCA adaptor dependant on the jboss transaction spi.
timfox Sep 9, 2009 9:00 AM (in response to ataylor)Great.
Can you close the JIRA when it's done?