I will do that now. Thanks for the help
gnodet wrote: > > Nice ! You should create a JIRA on Ode so that it can be fixed in the > next > release. > > On Nov 29, 2007 11:33 AM, Jan Arend Jansen <[EMAIL PROTECTED]> wrote: > >> >> Ok, I found the solution! >> >> I tried fiddeling with the >> component-class-loader-delegation="self-first" >> bootstrap-class-loader-delegation="parent-first" >> settings of the jbi.xml of ode-jbi, but to no effect. >> >> I than modified the ode-jbi-1.1.zip file. I added >> <path-element>lib/geronimo-connector-1.2-beta.jar</path-element> >> to both <component-class-path> and <bootstrap-class-path> >> and >> geronimo-connector-1.2-beta.jar >> to the lib dir. Deleted the data dir in SM and copied the modified >> ode-jbi-1.1.zip to hotdeploy/ >> >> That seems to do the trick.....so the classloader config was ok, only a >> library was missing from ode which was available in a higher version in >> servicemix, so the classloader loaded it from servicemix. >> >> Regards, >> Jan Arend >> >> Jan Arend Jansen wrote: >> > >> > That sounds like the 'switch' I was looking for....I will give it a >> try, >> > thanks! I'll post the results. >> > >> > >> > gnodet wrote: >> >> >> >> Have you tried to rebuild the Ode SE with a self-first classloader >> >> instead >> >> of a parent-first classloader ? >> >> This can be done in the META-INF/jbi.xml descriptor. >> >> >> >> On Nov 29, 2007 9:55 AM, Jan Arend Jansen <[EMAIL PROTECTED]> wrote: >> >> >> >>> >> >>> Hi, >> >>> >> >>> I'd like to use a BPEL engine in combination with CXF components on >> >>> ServiceMix 3.2. ODE seems to be ServiceMix's BPEL engine of choice, >> but >> >>> ODE-jbi-1.1 does not install on SM 3.2 due to a version conflict in >> the >> >>> geronimo libraries discussed earlier in this mailing list. >> >>> >> >>> Architecturally I think a SE should have a scoped classloader that >> >>> prioritizes local SE libraries over the servicemix libraries. >> Otherwise >> >>> you >> >>> will never be able to intergrate a non-servicemix maintained SE, >> beause >> >>> of >> >>> potentential library conflicts. You can't really expect ODE to comply >> to >> >>> the >> >>> versions of libraries that ServiceMix uses, can you? Is there a >> >>> mechanism >> >>> in >> >>> SM to force this? >> >>> >> >>> I've tried to use the suggested workaround by creating a datasource >> on >> >>> ServiceMix level that ODE SE can use (as suggested by Alex in another >> >>> thread). That works, but the problem I run into is that this database >> >>> does >> >>> not have the ODE schema auto-generated, so installation still >> fails.... >> >>> >> >>> Any suggestions how I could use a (not necessarilly ODE) BPEL engine >> in >> >>> combination with CXF with ServiceMix? >> >>> >> >>> Thanks, >> >>> Jan Arend >> >>> -- >> >>> View this message in context: >> >>> >> http://www.nabble.com/Servicemix-3.2-and-ODE-1.1-install-error-tf4895765s12049.html#a14021370 >> >>> Sent from the ServiceMix - User mailing list archive at Nabble.com. >> >>> >> >>> >> >> >> >> >> >> -- >> >> Cheers, >> >> Guillaume Nodet >> >> ------------------------ >> >> Blog: http://gnodet.blogspot.com/ >> >> >> >> >> > >> > >> >> -- >> View this message in context: >> http://www.nabble.com/Servicemix-3.2-and-ODE-1.1-install-error-tf4895765s12049.html#a14022967 >> Sent from the ServiceMix - User mailing list archive at Nabble.com. >> >> > > > -- > Cheers, > Guillaume Nodet > ------------------------ > Blog: http://gnodet.blogspot.com/ > > -- View this message in context: http://www.nabble.com/Servicemix-3.2-and-ODE-1.1-install-error-tf4895765s12049.html#a14024594 Sent from the ServiceMix - User mailing list archive at Nabble.com.
