[
https://issues.apache.org/jira/browse/ODE-302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12637088#action_12637088
]
Mateusz Nowakowski commented on ODE-302:
----------------------------------------
For these people who use Fuse/Servicemix (probably PETALS too) with ODE JBI
1.2 distribution and have problems with ODE database.
ODE binding component contains Derby database bundled into zip file, and this
database is extracted while deploying ODE into ServiceMix.
So the easiest working solution is to add JNDI entry (jndi.xml) with unzipped
database path:
<util:map id="jndiEntries">
(...)
<entry key="java:comp/env/jdbc/ode">
<bean class="org.apache.derby.jdbc.EmbeddedDataSource">
<property name="databaseName"
value="../smx/components/OdeBpelEngine/version_1/jpadb"/>
<property name="createDatabase" value="create"/>
<property name="user" value="sa"/>
</bean>
</entry>
(...)
</util:map>
and make sure that
ode-jbi.properties has such lines:
ode-jbi.db.mode=EXTERNAL
(...)
ode-jbi.db.ext.dataSource=java:comp/env/jdbc/ode
(embedded and internal database entries should be commented)
--
Regards
Mateusz Nowakowski
> 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
> 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.
-
You can reply to this email to add a comment to the issue online.
