[
https://issues.jboss.org/browse/JBTM-2062?page=com.atlassian.jira.plugin....
]
Michael Musgrove reopened JBTM-2062:
------------------------------------
The current implementation expects the client to supply a JNDI provider and the
implementation is then responsible for binding datasources. This means that the datasource
classes must be on the classpath which is a problem for the targeted ceylon version
(version 1.0 does not allow dynamic loading of modules).
In view of this issue and since the client is already required to supply the provider It
makes more sense to move the datasources binding responsibility into the client.
Consequently, I have reopened the JIRA to remove the datasource binding functionality.
Add support for ceylon
-----------------------
Key: JBTM-2062
URL:
https://issues.jboss.org/browse/JBTM-2062
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: SPI
Affects Versions: 5.0.0.CR2
Reporter: Michael Musgrove
Assignee: Michael Musgrove
Fix For: 5.0.0.CR3
I need an interface to start and stop the transaction service. The start method should
check to see if there is a JNDI provider present and, if so, make sure that our standard
interfaces are bound to that provider (UserTransaction, JTATransactionManager and
TransactionSynchronizationRegistry). Also, behind the scenes, it should register
TransactionDriver with java.sql.DriverManager and bind any required datasources into the
JNDI tree.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira