L.S., This is probably being caused by the way classloading works in JBI -- by default, the SU has a parent-first classloading mechanism so it will start looking in the component/container classpath before loading classes from the SU. By putting the required jars in the lib/optional directory, they're being considered part of the container classpath and that's why this fixes the issue.
You should be able to resolve this by explicitly configuring the SU to use self-first classloading as explained in http://servicemix.apache.org/classloaders.html. If you're going to build multiple SU that use the same libraries, you might also want to consider packaging those up as a shared library and reference that from your SU (explained on the same wiki page). Regards, Gert Vanthienen ------------------------ Open Source SOA: http://fusesource.com Blog: http://gertvanthienen.blogspot.com/ On 13 February 2010 17:56, Alexanderz <[email protected]> wrote: > > Hi! > > Does anyone have an example of using the spring script > beans(http://static.springsource.org/spring/docs/2.5.x/reference/dynamic-language.html) > in SU without servicemix-script or servicemix-scripting SEs in SMX 3? > > For example I would like to implement custom cxf-api interceptor or custom > predicate for eip:content-base-router on groovy or jruby spring beans. But > It seems I've faced with classloading problem: > > > 1) <loc-message>org/jruby/exceptions/JumpException</loc-message> > > <stack-trace><