L.S.,
This behavior is OK when you're building a SU. By specifying
servicemix-eip as a dependency on the SU pom.xml, you are actually
creating a SU targeted at the servicemix-eip JBI Component. (Cfr.
http://servicemix.apache.org/23-beginner-configuring-the-servicemix-file-su.html
where the SU becomes a servicemix-file SU). There is no need for the SU
to have a classpath entry. Moreover, you would only have to add an
xbean.xml file to configure the EIP SU (i.e. no servicemix.xml file).
On the other hand, if you are using a servicemix.xml file for using
ServiceMix in embedded mode, you don't have to create SU/SA JBI artifacts.
It's hard to tell where to go with the information you provided us.
Could you explain what you are trying to do or post some code examples
for us to look at?
Regards,
Gert
Sai wrote:
Hi,
I am using servicemix 3.2.1 on jdk6.
I given servicemix.xml with classpath as below
<classpath>
<location>.</location>
<location>lib/servicemix-eip-3.2.1.jar</location>
</classpath>.
pom.xml has dependency of servicemix-eip-3.2.1.jar, when done build the SU
it is not keeping the jar in lib folder.
Though same is working fine with servicemix-components-3.2.1.jar ,other
jars.
Anything wrong with eip ?
