Hi Bruce I am using 3.1 because of issues with 3.1.1 POMs (I am not quite sure if that is still the issue now). Unfortunately our project is a high-pressured proof of concept and so we did not pay close attention to keeping the components' name appart and I think that maybe the issue of the bad JBI.xml file.
The original version of EIP I used was from 3.1 even though I am not quite sure where it came from. I assume it came from the binary drop's component directory. This one did not deploy correctly but seems not to be responsible for the missing EIP namespace because my SA deployed even though the EIP SU did not start because of the missing EIP BC. A rebuilt from the source made it deploy and also made my EIP SU start. Now I cannot reproduce the problem anymore for whatever reason. One major concern I have with ServiceMix is that from time to time the server ends up in a bad state when using the file based deployment. Thanks - Andy -- View this message in context: http://www.nabble.com/Servicemix-EIP-Namespace-Problems-tf4402754s12049.html#a12576229 Sent from the ServiceMix - User mailing list archive at Nabble.com.
