[jira] Created: (MILYN-392) Make the JndiDataSource JTA compatible
|
View:
New views
7 Messages
—
Rating Filter:
Alert me
|
 |
[jira] Created: (MILYN-392) Make the JndiDataSource JTA compatible
by JIRA jira@codehaus.org
::
Rate this Message:
Make the JndiDataSource JTA compatible
-------------------------------------- Key: MILYN-392 URL: http://jira.codehaus.org/browse/MILYN-392 Project: Milyn Issue Type: Task Components: Smooks Core Reporter: Maurice Zeijen Assignee: Maurice Zeijen Fix For: Smooks v1.3 The current JndiDatasource is not JTA compatible. It should be able to handle JTA local transactions and XA transactions. We need to add the following properties and behaviour: transactionManager:JDBC/JTA/EXTERNAL (default: JDBC) JDBC: use commit/rollback method from connection object JTA: use commit/rollback methods from the UserTransaction object EXTERNAL: transaction is to be managed by an external manager. So don't call any commit/rollback methods userTransaction: jndi path to the UserTransaction object (default: ) setAutoCommitAllowed: If "true" then the AutoCommit method of the Connection object will be called. If "false" then it wil not be called. (default: true) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
|
[jira] Work started: (MILYN-392) Make the JndiDataSource JTA compatible
by JIRA jira@codehaus.org
::
Rate this Message:
[ http://jira.codehaus.org/browse/MILYN-392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on MILYN-392 started by Maurice Zeijen. > Make the JndiDataSource JTA compatible > -------------------------------------- > > Key: MILYN-392 > URL: http://jira.codehaus.org/browse/MILYN-392 > Project: Milyn > Issue Type: Task > Components: Smooks Core > Reporter: Maurice Zeijen > Assignee: Maurice Zeijen > Fix For: Smooks v1.3 > > > The current JndiDatasource is not JTA compatible. It should be able to handle JTA local transactions and XA transactions. We need to add the following properties and behaviour: > transactionManager:JDBC/JTA/EXTERNAL (default: JDBC) > JDBC: use commit/rollback method from connection object > JTA: use commit/rollback methods from the UserTransaction object > EXTERNAL: transaction is to be managed by an external manager. So don't call any commit/rollback methods > userTransaction: jndi path to the UserTransaction object (default: ) > setAutoCommitAllowed: If "true" then the AutoCommit method of the Connection object will be called. If "false" then it wil not be called. (default: true) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
|
[jira] Commented: (MILYN-392) Make the JndiDataSource JTA compatible
by JIRA jira@codehaus.org
::
Rate this Message:
[ http://jira.codehaus.org/browse/MILYN-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=198076#action_198076 ] Maurice Zeijen commented on MILYN-392: -------------------------------------- Managing a JTA transaction with the JndiDatasource isn't decently possible. Another dedicated visitor is required to manage such transactions. That is why I decided that I need to do things a bit different: The following two new attributes will be added: manageTransaction: If "true" then the datasource will do transaction operations (commit, rollback, setAutoCommit (if allowed)). If "false" then the datasource is not allowed to do any transaction operations.(default: true) setAutoCommitAllowed: If "true" then the AutoCommit method of the Connection object will be called. If "false" then it will not be called. If "manageTransaction" is set to "false" then this attribute and the 'autoCommit' attribute has no effect. (default: true) > Make the JndiDataSource JTA compatible > -------------------------------------- > > Key: MILYN-392 > URL: http://jira.codehaus.org/browse/MILYN-392 > Project: Milyn > Issue Type: Task > Components: Smooks Core > Reporter: Maurice Zeijen > Assignee: Maurice Zeijen > Fix For: Smooks v1.3 > > > The current JndiDatasource is not JTA compatible. It should be able to handle JTA local transactions and XA transactions. We need to add the following properties and behaviour: > transactionManager:JDBC/JTA/EXTERNAL (default: JDBC) > JDBC: use commit/rollback method from connection object > JTA: use commit/rollback methods from the UserTransaction object > EXTERNAL: transaction is to be managed by an external manager. So don't call any commit/rollback methods > userTransaction: jndi path to the UserTransaction object (default: ) > setAutoCommitAllowed: If "true" then the AutoCommit method of the Connection object will be called. If "false" then it wil not be called. (default: true) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
|
[jira] Commented: (MILYN-392) Make the JndiDataSource JTA compatible
by JIRA jira@codehaus.org
::
Rate this Message:
[ http://jira.codehaus.org/browse/MILYN-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=198078#action_198078 ] Tom Fennelly commented on MILYN-392: ------------------------------------ Hey Maurice... can you explain the issues? On the dev list perhaps. > Make the JndiDataSource JTA compatible > -------------------------------------- > > Key: MILYN-392 > URL: http://jira.codehaus.org/browse/MILYN-392 > Project: Milyn > Issue Type: Task > Components: Smooks Core > Reporter: Maurice Zeijen > Assignee: Maurice Zeijen > Fix For: Smooks v1.3 > > > The current JndiDatasource is not JTA compatible. It should be able to handle JTA local transactions and XA transactions. We need to add the following properties and behaviour: > transactionManager:JDBC/JTA/EXTERNAL (default: JDBC) > JDBC: use commit/rollback method from connection object > JTA: use commit/rollback methods from the UserTransaction object > EXTERNAL: transaction is to be managed by an external manager. So don't call any commit/rollback methods > userTransaction: jndi path to the UserTransaction object (default: ) > setAutoCommitAllowed: If "true" then the AutoCommit method of the Connection object will be called. If "false" then it wil not be called. (default: true) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
|
[jira] Resolved: (MILYN-392) Make the JndiDataSource JTA compatible
by JIRA jira@codehaus.org
::
Rate this Message:
[ http://jira.codehaus.org/browse/MILYN-392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maurice Zeijen resolved MILYN-392. ---------------------------------- Resolution: Fixed > Make the JndiDataSource JTA compatible > -------------------------------------- > > Key: MILYN-392 > URL: http://jira.codehaus.org/browse/MILYN-392 > Project: Milyn > Issue Type: Task > Components: Smooks Core > Reporter: Maurice Zeijen > Assignee: Maurice Zeijen > Fix For: Smooks v1.3 > > > The current JndiDatasource is not JTA compatible. It should be able to handle JTA local transactions and XA transactions. We need to add the following properties and behaviour: > transactionManager:JDBC/JTA/EXTERNAL (default: JDBC) > JDBC: use commit/rollback method from connection object > JTA: use commit/rollback methods from the UserTransaction object > EXTERNAL: transaction is to be managed by an external manager. So don't call any commit/rollback methods > userTransaction: jndi path to the UserTransaction object (default: ) > setAutoCommitAllowed: If "true" then the AutoCommit method of the Connection object will be called. If "false" then it wil not be called. (default: true) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
|
[jira] Reopened: (MILYN-392) Make the JndiDataSource JTA compatible
by JIRA jira@codehaus.org
::
Rate this Message:
[ http://jira.codehaus.org/browse/MILYN-392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maurice Zeijen reopened MILYN-392: ---------------------------------- It seems that the Connection object changed in Java 1.6. This means that my current solution won't work. I will try to fix it asap. > Make the JndiDataSource JTA compatible > -------------------------------------- > > Key: MILYN-392 > URL: http://jira.codehaus.org/browse/MILYN-392 > Project: Milyn > Issue Type: Task > Components: Smooks Core > Reporter: Maurice Zeijen > Assignee: Maurice Zeijen > Fix For: Smooks v1.3 > > > The current JndiDatasource is not JTA compatible. It should be able to handle JTA local transactions and XA transactions. We need to add the following properties and behaviour: > transactionManager:JDBC/JTA/EXTERNAL (default: JDBC) > JDBC: use commit/rollback method from connection object > JTA: use commit/rollback methods from the UserTransaction object > EXTERNAL: transaction is to be managed by an external manager. So don't call any commit/rollback methods > userTransaction: jndi path to the UserTransaction object (default: ) > setAutoCommitAllowed: If "true" then the AutoCommit method of the Connection object will be called. If "false" then it wil not be called. (default: true) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
|
[jira] Resolved: (MILYN-392) Make the JndiDataSource JTA compatible
by JIRA jira@codehaus.org
::
Rate this Message:
[ http://jira.codehaus.org/browse/MILYN-392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maurice Zeijen resolved MILYN-392. ---------------------------------- Resolution: Fixed Did some refactoring which resulted in cleaner and better code. The only downside is that I need to set and retrieve an extra execution context attribute. > Make the JndiDataSource JTA compatible > -------------------------------------- > > Key: MILYN-392 > URL: http://jira.codehaus.org/browse/MILYN-392 > Project: Milyn > Issue Type: Task > Components: Smooks Core > Reporter: Maurice Zeijen > Assignee: Maurice Zeijen > Fix For: Smooks v1.3 > > > The current JndiDatasource is not JTA compatible. It should be able to handle JTA local transactions and XA transactions. We need to add the following properties and behaviour: > transactionManager:JDBC/JTA/EXTERNAL (default: JDBC) > JDBC: use commit/rollback method from connection object > JTA: use commit/rollback methods from the UserTransaction object > EXTERNAL: transaction is to be managed by an external manager. So don't call any commit/rollback methods > userTransaction: jndi path to the UserTransaction object (default: ) > setAutoCommitAllowed: If "true" then the AutoCommit method of the Connection object will be called. If "false" then it wil not be called. (default: true) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
| Free embeddable forum powered by Nabble | Forum Help |
