[
https://issues.apache.org/jira/browse/ODE-302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13750903#comment-13750903
]
Hudson commented on ODE-302:
----------------------------
SUCCESS: Integrated in ODE-trunk-jdk6 #733 (See
[https://builds.apache.org/job/ODE-trunk-jdk6/733/])
fixing ODE-302 (vanto: rev 558b2c67ab45dd39e9da982cb9cb3cc32debabbc)
* jbi/src/main/java/org/apache/ode/jbi/OdeLifeCycle.java
* jbi/src/main/java/org/apache/ode/jbi/OdeContext.java
* Rakefile
fixing a bug for ODE-302 (vanto: rev 19854fb90bc4393ca179099de185a91ec70998e9)
* jbi/src/main/java/org/apache/ode/jbi/OdeContext.java
> Use embedded TransactionManager if database mode is EMBEDDED or INTERNAL
> ------------------------------------------------------------------------
>
> Key: ODE-302
> URL: https://issues.apache.org/jira/browse/ODE-302
> Project: ODE
> Issue Type: Bug
> Components: JBI Integration
> Reporter: Alex Boisvert
> Assignee: Tammo van Lessen
> Labels: patch
> Fix For: 1.3.6, 1.4
>
> Attachments: ODE302.patch.txt
>
>
> Ode should not use the TransactionManager provided by the JBI container in
> EMBEDDED and INTERNAL database modes since it creates its own DataSource
> which are not under the responsibility of the container's TransactionManager.
> This happened to work with ServiceMix since it uses the same
> TransactionManager (Geronimo's), but it's not something we can assume in
> other JBI environments.
--
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
