Hi Alex, I really think that it will be cool but same for me, I am quite busy preparing cool things for PEtALS v3. I will try to do something (in the next months...) but I can promise nothing.
Christophe Alex Boisvert-3 wrote: > > Hi Christophe, > > I agree with you; we still need to clean up a few things to get Ode > working > in PEtALS. It's been on my list of things to do although other things > keep > piling up.... If you want to submit patches that would improve the > situation, I'll be happy to review them and get them incorporated into the > codebase. > > alex > > > On Tue, Nov 4, 2008 at 3:53 AM, Christophe Hamerling < > [EMAIL PROTECTED]> wrote: > >> >> Hi Alex, >> >> I have checked the trunk and I see that there is no changes on the way >> the >> embedded mode works. >> I really think that this component MUST work without any additional >> configuration and without an external datasource. >> The fact that in the embedded mode, the transaction manager is casted >> into >> RecoverableTransactionManager is not JBI compliant. ServiceMix probably >> uses >> this Geronimo implementation but other JBI implementations do not. >> I do not check all the sources but is it really imporant to get a >> RecoverableTransactionManager? If yes, maybe you can create a mode with >> a >> standard transaction manager. >> I think that it is quite important for ODE to easliy run on PEtALS also >> (of >> course for PEtALS too :) ). >> Unfortunately I have conflicts with rake and buildr on my ubuntu, hope to >> solve it soon and maybe to send a patch... >> >> Regards, >> Christophe >> >> >> Alex Boisvert-3 wrote: >> > >> > Hi Richard, >> > >> > I recommend using the "EXTERNAL" datasource configuration with Ode and >> > looking up the DataSource using JNDI. This way, Ode will use the JBI >> > container's transaction manager (which is always preferable) and the >> same >> > transaction manager will manage the datasource. >> > >> > In ode-jbi.properties, this would correspond to: >> > >> > ode-jbi.db.mode=EXTERNAL >> > ode-jbi.db.ext.dataSource=java:comp/env/jdbc/ode (you can configure >> this >> > string to match your datasource >> > >> > alex >> > >> > On Wed, Jun 11, 2008 at 2:12 AM, <[EMAIL PROTECTED]> >> > wrote: >> > >> >> hello, >> >> >> >> I have tried to deploy on two JBI implementations your 1.2RC1 version >> >> (found >> >> on >> >> >> >> >> http://people.apache.org/~mriou/ode-1.2RC1/org/apache/ode/apache-ode-jbi/1.2<http://people.apache.org/%7Emriou/ode-1.2RC1/org/apache/ode/apache-ode-jbi/1.2> >> >> RC1/< >> http://people.apache.org/%7Emriou/ode-1.2RC1/org/apache/ode/apache-ode-jbi/1.2RC1/ >> > >> >> ) >> >> I play with ServiceMix-3.2.1 and PetALS-2.1.1.1 versions. >> >> >> >> With ServiceMix, there is no major problem : I copy the two SM >> components >> >> servicemix-shared-3.2.1-installer.zip and >> >> servicemix-http-3.2.1-installer.zip in the ServiceMix 'hotdeploy' >> >> directory. >> >> Then I copy the ODE ZIP SE ode-jbi-1.2RC1.zip and the example >> >> HelloWorld2-sa.zip. finally I run the client test with Ant, and I >> obtain >> >> the >> >> good message in return of the process invocation. So with ServiceMix >> all >> >> is >> >> OK. >> >> >> >> With PEtALS, unfortunatly when I deploy the ZIP SE component (file >> >> ode-jbi-1.2RC1.zip), that fails at installation-time with an error >> >> message >> >> : >> >> >> >> [petals.InstallationService] >> InstallationServiceImpl.loadNewInstaller() >> >> Component succesfully installed: OdeBpelEngine >> >> 10:30:06,406 ERROR OdeLifeCycle:178 - Database configuration error. >> >> java.lang.RuntimeException: TransactionManager is not recoverable. >> >> at >> >> org.apache.ode.il.dbutil.Database.initInternalDb(Database.java:179) >> >> at >> >> org.apache.ode.il.dbutil.Database.initEmbeddedDb(Database.java:232) >> >> at >> >> org.apache.ode.il.dbutil.Database.initDataSource(Database.java:147) >> >> at org.apache.ode.il.dbutil.Database.start(Database.java:99) >> >> at >> >> org.apache.ode.jbi.OdeLifeCycle.initDataSource(OdeLifeCycle.java:175) >> >> at org.apache.ode.jbi.OdeLifeCycle.init(OdeLifeCycle.java:113) >> >> at >> >> >> >> >> org.ow2.petals.container.thread.ComponentLifeCycleThread.doTask(ComponentLif >> >> eCycleThread.java:101) >> >> at >> >> >> org.ow2.petals.container.thread.AbstractThread.run(AbstractThread.java:106) >> >> >> >> >> >> I have a bit analyse ODE sources and I don't understand why the >> >> transaction >> >> manager, instancied from the JBI context (getTransactionManager) >> should >> >> be >> >> an instance of 'RecoverableTransactionManager' (=a class of geronimo >> jar >> >> not >> >> known of PEtALS). I think there is a suspicious dependancy with >> >> ServiceMix >> >> in this part of the code. >> >> >> >> Matthieu, in a previous mail you said that it may that I use an >> "external >> >> transaction manager". How is it possible as I don't touch anything in >> the >> >> ODE configuration (I use the embedded Derby database) ? Could you >> develop >> >> this idea ? >> >> >> >> Besides, I use Java6 with ODE. Is it correct ? (I read somewhere that >> ODE >> >> only supports Java5 but I'm not sure) >> >> >> >> >> >> Thanks for your help. >> >> >> >> Richard. >> >> >> >> PS: >> >> For information, the PEtALS release I use has successfully passed in >> >> March >> >> 2008 the JBI compatibility test suite (JBI TCK). >> >> >> > >> > >> >> >> ----- >> Christophe Hamerling >> PEtALS ESB Project Leader >> http://petals.ow2.org http://petals.ow2.org >> SkypeMe on christophe.hamerling >> -- >> View this message in context: >> http://www.nabble.com/Pb-deployment-ODE-on-JBI-PEtALS-tp17778328p20319180.html >> Sent from the Apache Ode Dev mailing list archive at Nabble.com. >> >> > > ----- Christophe Hamerling PEtALS ESB Project Leader http://petals.ow2.org http://petals.ow2.org SkypeMe on christophe.hamerling -- View this message in context: http://www.nabble.com/Pb-deployment-ODE-on-JBI-PEtALS-tp17778328p20349983.html Sent from the Apache Ode Dev mailing list archive at Nabble.com.
