[ https://issues.jboss.org/browse/JBTM-809?page=com.atlassian.jira.plugin.s... ] Tom Jenkinson updated JBTM-809: ------------------------------- JBoss Forum Reference: http://community.jboss.org/thread/166568 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBTM-809?page=com.atlassian.jira.plugin.s... ] Mauro Molinari commented on JBTM-809: ------------------------------------- Is there any documentation that explains what is going on here? Will JBossTS be still usable for JDBC connections? In what would consist the migration? We're using JBossTS in a JTA infrastructure where database queries are done through JDBC. The client code just uses JDBC connections (obtained through the transactional driver), while the global JTA transaction is controlled using Spring JTA transaction manager. The JBossTS backend, through the transactional driver and some of our glue code, is obtaining JTA connections through XA data sources created using the DynamicClass mechanism. We're working outside JEE, just plain Tomcat + JBossTS + Spring. How will the scenario change with JCA? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBTM-809?page=com.atlassian.jira.plugin.s... ] Tom Jenkinson commented on JBTM-809: ------------------------------------ Hi Mauro, 1. There is no docs at the moment, I will run any changes passed the community first in the forum and we definitely dont want to break anything that can't be easily fixed :) 2. Definitely TS would still be usable for JDBC connections, all that would change would be the way the connection is retrieved (from JNDI) Hope that helps, Tom -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira