I'm not sure I understand you, but to my understanding you install JBI components and you deploy service assemblies. So, if you have a JBI component, you need to install this one before you can deploy your servcie assembly utilizing it. So, you shouldn't embedd the JBI component classes into your SU/SA. Possibly you're talking about light-weight component classes? In that case, those aren't JBI components and should be included in the SU and the JBI component that you need to install is the lwcontainer.
Ralf Wunsch wrote: > > Hello, > > I have found two ways to use components i a service unit (correct me if i > am not on the right way). > At first i can deploy a JBI component (i am using the JBoss platform and > the maven plugins to build the components installer zip file). > In the other case i am embedding the components classes (the components > jar file) into the service units zip file (the service units classpath > points to the embedded jars). > If i use the second case only the embeddend code wil be used. If i use the > first way the installed JBI component will be used whether if i have > embedded the components code in the service unit or not. > http://www.nabble.com/file/3598/sa-su-classloading.png > Three questions: > Are both ways right ways? > Why has the component deployed separately a higher priority than the > embedded component? > How can i ensure that modifications of a component can be used by some > service units (or service assemblies) without side effects to the other > deployed service units (older units which will be adapted later)? > > Thanks for your assistance > Ralf Wunsch > -- View this message in context: http://www.nabble.com/service-unit-classloading-tf2422083.html#a6790655 Sent from the ServiceMix - User mailing list archive at Nabble.com.
