You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2011/08/27 09:57:28 UTC
[jira] [Created] (CAMEL-4387) camel-ibatis - Allow to more easily
configure the TX isolation level on processing strategy
camel-ibatis - Allow to more easily configure the TX isolation level on processing strategy
-------------------------------------------------------------------------------------------
Key: CAMEL-4387
URL: https://issues.apache.org/jira/browse/CAMEL-4387
Project: Camel
Issue Type: Improvement
Components: camel-ibatis
Reporter: Claus Ibsen
Priority: Minor
Fix For: 2.9.0
The DefaultIBatisProcessingStategy should have a getter/setter for transaction isolation level: eg Connection.TRANSACTION_READ_COMMITTED etc.
See java.sql.Connection for possible values.
This is in use when {{onConsume}} is being used.
The default TX isolation does not work well with Oracle etc. See nabble
http://camel.465427.n5.nabble.com/Camel-Ibatis-consumer-onConsume-with-Oracle-throws-transaction-isolation-level-error-tp4731035p4731035.html
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CAMEL-4387) camel-ibatis - Allow to more easily
configure the TX isolation level on processing strategy
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-4387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen updated CAMEL-4387:
-------------------------------
Estimated Complexity: Novice (was: Unknown)
> camel-ibatis - Allow to more easily configure the TX isolation level on processing strategy
> -------------------------------------------------------------------------------------------
>
> Key: CAMEL-4387
> URL: https://issues.apache.org/jira/browse/CAMEL-4387
> Project: Camel
> Issue Type: Improvement
> Components: camel-ibatis
> Reporter: Claus Ibsen
> Priority: Minor
> Fix For: 2.9.0
>
>
> The DefaultIBatisProcessingStategy should have a getter/setter for transaction isolation level: eg Connection.TRANSACTION_READ_COMMITTED etc.
> See java.sql.Connection for possible values.
> This is in use when {{onConsume}} is being used.
> The default TX isolation does not work well with Oracle etc. See nabble
> http://camel.465427.n5.nabble.com/Camel-Ibatis-consumer-onConsume-with-Oracle-throws-transaction-isolation-level-error-tp4731035p4731035.html
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CAMEL-4387) camel-ibatis - Allow to more easily
configure the TX isolation level on processing strategy
Posted by "Ioannis Canellos (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-4387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ioannis Canellos resolved CAMEL-4387.
-------------------------------------
Resolution: Fixed
Patch has been applied and documentation has been updated.
> camel-ibatis - Allow to more easily configure the TX isolation level on processing strategy
> -------------------------------------------------------------------------------------------
>
> Key: CAMEL-4387
> URL: https://issues.apache.org/jira/browse/CAMEL-4387
> Project: Camel
> Issue Type: Improvement
> Components: camel-ibatis
> Reporter: Claus Ibsen
> Assignee: Ioannis Canellos
> Priority: Minor
> Fix For: 2.9.0
>
> Attachments: CAMEL-4387-patch.txt
>
>
> The DefaultIBatisProcessingStategy should have a getter/setter for transaction isolation level: eg Connection.TRANSACTION_READ_COMMITTED etc.
> See java.sql.Connection for possible values.
> This is in use when {{onConsume}} is being used.
> The default TX isolation does not work well with Oracle etc. See nabble
> http://camel.465427.n5.nabble.com/Camel-Ibatis-consumer-onConsume-with-Oracle-throws-transaction-isolation-level-error-tp4731035p4731035.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-4387) camel-ibatis - Allow to more easily
configure the TX isolation level on processing strategy
Posted by "Owen Toalson (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-4387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13131364#comment-13131364 ]
Owen Toalson commented on CAMEL-4387:
-------------------------------------
Thanks Claus and loannis! I will try out changes.
> camel-ibatis - Allow to more easily configure the TX isolation level on processing strategy
> -------------------------------------------------------------------------------------------
>
> Key: CAMEL-4387
> URL: https://issues.apache.org/jira/browse/CAMEL-4387
> Project: Camel
> Issue Type: Improvement
> Components: camel-ibatis
> Reporter: Claus Ibsen
> Assignee: Ioannis Canellos
> Priority: Minor
> Fix For: 2.9.0
>
> Attachments: CAMEL-4387-patch.txt
>
>
> The DefaultIBatisProcessingStategy should have a getter/setter for transaction isolation level: eg Connection.TRANSACTION_READ_COMMITTED etc.
> See java.sql.Connection for possible values.
> This is in use when {{onConsume}} is being used.
> The default TX isolation does not work well with Oracle etc. See nabble
> http://camel.465427.n5.nabble.com/Camel-Ibatis-consumer-onConsume-with-Oracle-throws-transaction-isolation-level-error-tp4731035p4731035.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CAMEL-4387) camel-ibatis - Allow to more easily
configure the TX isolation level on processing strategy
Posted by "Ioannis Canellos (Assigned) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-4387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ioannis Canellos reassigned CAMEL-4387:
---------------------------------------
Assignee: Ioannis Canellos
> camel-ibatis - Allow to more easily configure the TX isolation level on processing strategy
> -------------------------------------------------------------------------------------------
>
> Key: CAMEL-4387
> URL: https://issues.apache.org/jira/browse/CAMEL-4387
> Project: Camel
> Issue Type: Improvement
> Components: camel-ibatis
> Reporter: Claus Ibsen
> Assignee: Ioannis Canellos
> Priority: Minor
> Fix For: 2.9.0
>
>
> The DefaultIBatisProcessingStategy should have a getter/setter for transaction isolation level: eg Connection.TRANSACTION_READ_COMMITTED etc.
> See java.sql.Connection for possible values.
> This is in use when {{onConsume}} is being used.
> The default TX isolation does not work well with Oracle etc. See nabble
> http://camel.465427.n5.nabble.com/Camel-Ibatis-consumer-onConsume-with-Oracle-throws-transaction-isolation-level-error-tp4731035p4731035.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-4387) camel-ibatis - Allow to more easily
configure the TX isolation level on processing strategy
Posted by "Claus Ibsen (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-4387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13116213#comment-13116213 ]
Claus Ibsen commented on CAMEL-4387:
------------------------------------
Thanks Ioannis. Patch applied.
Do you mind updating the wiki documentation, and then resolve this ticket.
> camel-ibatis - Allow to more easily configure the TX isolation level on processing strategy
> -------------------------------------------------------------------------------------------
>
> Key: CAMEL-4387
> URL: https://issues.apache.org/jira/browse/CAMEL-4387
> Project: Camel
> Issue Type: Improvement
> Components: camel-ibatis
> Reporter: Claus Ibsen
> Assignee: Ioannis Canellos
> Priority: Minor
> Fix For: 2.9.0
>
> Attachments: CAMEL-4387-patch.txt
>
>
> The DefaultIBatisProcessingStategy should have a getter/setter for transaction isolation level: eg Connection.TRANSACTION_READ_COMMITTED etc.
> See java.sql.Connection for possible values.
> This is in use when {{onConsume}} is being used.
> The default TX isolation does not work well with Oracle etc. See nabble
> http://camel.465427.n5.nabble.com/Camel-Ibatis-consumer-onConsume-with-Oracle-throws-transaction-isolation-level-error-tp4731035p4731035.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CAMEL-4387) camel-ibatis - Allow to more easily
configure the TX isolation level on processing strategy
Posted by "Owen Toalson (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-4387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Owen Toalson updated CAMEL-4387:
--------------------------------
Comment: was deleted
(was: Thanks Claus and loannis! I will try out changes.)
> camel-ibatis - Allow to more easily configure the TX isolation level on processing strategy
> -------------------------------------------------------------------------------------------
>
> Key: CAMEL-4387
> URL: https://issues.apache.org/jira/browse/CAMEL-4387
> Project: Camel
> Issue Type: Improvement
> Components: camel-ibatis
> Reporter: Claus Ibsen
> Assignee: Ioannis Canellos
> Priority: Minor
> Fix For: 2.9.0
>
> Attachments: CAMEL-4387-patch.txt
>
>
> The DefaultIBatisProcessingStategy should have a getter/setter for transaction isolation level: eg Connection.TRANSACTION_READ_COMMITTED etc.
> See java.sql.Connection for possible values.
> This is in use when {{onConsume}} is being used.
> The default TX isolation does not work well with Oracle etc. See nabble
> http://camel.465427.n5.nabble.com/Camel-Ibatis-consumer-onConsume-with-Oracle-throws-transaction-isolation-level-error-tp4731035p4731035.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-4387) camel-ibatis - Allow to more easily
configure the TX isolation level on processing strategy
Posted by "Owen Toalson (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-4387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13131363#comment-13131363 ]
Owen Toalson commented on CAMEL-4387:
-------------------------------------
Thanks Claus and loannis! I will try out changes.
> camel-ibatis - Allow to more easily configure the TX isolation level on processing strategy
> -------------------------------------------------------------------------------------------
>
> Key: CAMEL-4387
> URL: https://issues.apache.org/jira/browse/CAMEL-4387
> Project: Camel
> Issue Type: Improvement
> Components: camel-ibatis
> Reporter: Claus Ibsen
> Assignee: Ioannis Canellos
> Priority: Minor
> Fix For: 2.9.0
>
> Attachments: CAMEL-4387-patch.txt
>
>
> The DefaultIBatisProcessingStategy should have a getter/setter for transaction isolation level: eg Connection.TRANSACTION_READ_COMMITTED etc.
> See java.sql.Connection for possible values.
> This is in use when {{onConsume}} is being used.
> The default TX isolation does not work well with Oracle etc. See nabble
> http://camel.465427.n5.nabble.com/Camel-Ibatis-consumer-onConsume-with-Oracle-throws-transaction-isolation-level-error-tp4731035p4731035.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CAMEL-4387) camel-ibatis - Allow to more easily
configure the TX isolation level on processing strategy
Posted by "Ioannis Canellos (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-4387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ioannis Canellos updated CAMEL-4387:
------------------------------------
Attachment: CAMEL-4387-patch.txt
I am attaching a patch which adds a getter and setter on IBatisProcessingStrategy.
Added a getter and setter on IBatisEndpoint to set the isolation on the endpoint. The endpoint accepts the isolation using its name as declared in java.sql.Connection.
Finally added a unit tests, which mock the strategy in order to verify that the isolation is set properly etc.
> camel-ibatis - Allow to more easily configure the TX isolation level on processing strategy
> -------------------------------------------------------------------------------------------
>
> Key: CAMEL-4387
> URL: https://issues.apache.org/jira/browse/CAMEL-4387
> Project: Camel
> Issue Type: Improvement
> Components: camel-ibatis
> Reporter: Claus Ibsen
> Assignee: Ioannis Canellos
> Priority: Minor
> Fix For: 2.9.0
>
> Attachments: CAMEL-4387-patch.txt
>
>
> The DefaultIBatisProcessingStategy should have a getter/setter for transaction isolation level: eg Connection.TRANSACTION_READ_COMMITTED etc.
> See java.sql.Connection for possible values.
> This is in use when {{onConsume}} is being used.
> The default TX isolation does not work well with Oracle etc. See nabble
> http://camel.465427.n5.nabble.com/Camel-Ibatis-consumer-onConsume-with-Oracle-throws-transaction-isolation-level-error-tp4731035p4731035.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira