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/

Reply via email to