You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ode.apache.org by "Mateusz Nowakowski (JIRA)" <ji...@apache.org> on 2008/10/06 13:59:44 UTC

[jira] Commented: (ODE-302) Use embedded TransactionManager if database mode is EMBEDDED or INTERNAL

    [ 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.

RE: [jira] Commented: (ODE-302) Use embedded TransactionManager if database mode is EMBEDDED or INTERNAL

Posted by Richard AILLET <ri...@free.fr>.
Hi,

Sorry, I'm not agree with but your opinion. The solution you mentioned below is surely transposable to Fuse (based on ServieMix).
But it is not at all transposable to other JBI compliant implementations (openESB, PEtALS, Mule, etc..).

As I know, jndi.xml is a specific ServiceMix configuration file. There is no equivalent for other JBI implementations.

To succeed the integration of ODE in JBI implementations (other than ServiceMix or Fuse), it is needed to review the ODE SE component code and remove all adherence to ServiceMix and their internal libraries.

Regards,
Richard.

-----Message d'origine-----
De : Mateusz Nowakowski (JIRA) [mailto:jira@apache.org] 
Envoyé : lundi 6 octobre 2008 14:00
À : dev@ode.apache.org
Objet : [jira] Commented: (ODE-302) Use embedded TransactionManager if database mode is EMBEDDED or INTERNAL


    [ 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.

Re: [jira] Commented: (ODE-302) Use embedded TransactionManager if database mode is EMBEDDED or INTERNAL

Posted by Alex Boisvert <bo...@intalio.com>.
On Fri, Oct 10, 2008 at 6:09 PM, Richard AILLET <ri...@free.fr>wrote:

> To succeed the integration of ODE in JBI implementations (other than
> ServiceMix or Fuse), it is needed to review the ODE SE component code and
> remove all adherence to ServiceMix and their internal libraries.


There is no dependency on ServiceMix and its internal libraries in Ode.

We have a message mapper implementation that's specifically tailored for
ServiceMix users because some ServiceMix components are not compliant with
the JBI spec.  This being said, this message mapper is not the default (it
requires special configuration) and it does not depend on any ServiceMix
libraries.

I believe the only non-compliance with regards to the JBI specification in
Ode is the way the JNDI InitialContext is accessed.    Ode currently obtains
the InitialContext by doing "new InitialContext()" whereas it should be
retrieved from the ComponentContext.  (I've just created ODE-386 to track
this)

If you're aware of any other non-compliance, please open issues and we'll
fix them.

cheers,
alex