Jaxen classpath problem

[Eyji <ey...@gmail.com>]

I have a service assembly consisting of a couple of ligthweight components
(validation, drools). The jaxen-1.1-beta-9.jar is packaged in the /lib
directory of the lw-su, but is reported as missing when called upon, even if
I have a classpath-reference to the file in my servicemix.xml. However, if
the jar-file is copied to the servicemix lib-directory everything works OK.
Is there something I have missed?

Cheers for now,
/Eyji
-- 
View this message in context: http://www.nabble.com/Jaxen-classpath-problem-tf2859886s12049.html#a7990429
Sent from the ServiceMix - User mailing list archive at Nabble.com.

Re: Jaxen classpath problem

[Guillaume Nodet <gn...@gmail.com>]

If jaxen is referenced by servicemix expressions package, the jvm classloader
architecture needs jaxen to be available from the container classpath.
There is no way to workaround that easily, unfortunately: the only way would
be to copy the jaxen expression in your SU and use a self-first classloader
delegation (if you don't rename it).

On 12/20/06, Eyji <ey...@gmail.com> wrote:
>
> I have a service assembly consisting of a couple of ligthweight components
> (validation, drools). The jaxen-1.1-beta-9.jar is packaged in the /lib
> directory of the lw-su, but is reported as missing when called upon, even if
> I have a classpath-reference to the file in my servicemix.xml. However, if
> the jar-file is copied to the servicemix lib-directory everything works OK.
> Is there something I have missed?
>
> Cheers for now,
> /Eyji
> --
> View this message in context: http://www.nabble.com/Jaxen-classpath-problem-tf2859886s12049.html#a7990429
> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>
>


-- 
Cheers,
Guillaume Nodet