Hi Lukasz,

It *appears* I was able to get it to work correctly now.  I had an xbean
context loading inside the xbean context for the servicemix-bean SE in order
to do some advanced configuration.  I wasn't aware of how to easily use the
service unit xbean context to do what I wanted.  This internal context was
causing all kinds of problems when I moved my code to it's own Service
Engine, once I eliminated that internal context and moved everything to the
context that configures the SU, it appears things started to be found
correctly.  I looks like this is a limitation of the current xbean code.  It
just led to a ton of confusion since everything had worked in
servicemix-bean.  Anyhow, I think the problem is solved.

Thanks!
Ryan

On Tue, Jan 27, 2009 at 3:42 AM, Lukasz L. <[email protected]> wrote:

>
> The purpose is that classes in SU are for use in SU and shouldn't conflict
> with classes in other SU for the same SE (or any other SU), e.g. you may
> have two different SUs for bean component, both using Hibernate jars but in
> different versions.
> Classes in SE are used for SE implementation itself.
> But I can't explain why some of them are visible in SU and some not (I
> recall that JBI specification says something about hierarchy of
> classloaders
> in SE/SU so you may check there as well)
>
>
> Ryan Moquin wrote:
> >
> > Out of curiousity, what purpose do the classes in the lib directory of a
> > service engine perform compared to the classes in the lib directory of a
> > service unit?  What jars should be in which?  I'm seeing some odd stuff
> > where some classes are being found when starting my service unit which
> are
> > contained in a jar in my service engine, but other classes are said to
> not
> > be found by the service unit that are in the same jar file in the service
> > enginer as the other classes that were found.  Which seems odd.    I
> don't
> > have any problems deploying a service unit onto the service engine in an
> > servicemix from a unit test.  I'm a little puzzled on how this
> > classloading
> > works in a the standalone servicemix and tomcat servicemix.
> >
> > Thanks for any help!
> >
> > Ryan
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/Classloading-for-service-engine-vs.-service-unit-tp21670762p21681609.html
> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>
>

Reply via email to