[
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
