Hi, I am currently playing around with Open ESB and ServiceMix and have come to see that the CXF BC and SE provided with ServiceMix are quite sexy. So, since these components claim to be JBI compliant, I figured it'd be a good idea to just install them to the Open ESB container in glassfish and use their functionality. However, while deploying the installer zip files of the BC and SE, glassfish complained about the missing class org.apache.servicemix.MessageExchangeListener. Obviously, the components are dependent on the JBI container implementation. I am quite disappointed since one of the major arguments for JBI was to establish a runtime environment for JBI compliant components from multiple vendors that can be plugged into any compliant JBI container. However, this (as always) seems to be just fluff (see EJB etc).
Now, have the ServiceMix developers implemented this dependency by intention in order to keep others from using their components or is this just a design flaw? Regards, Kai -- View this message in context: http://www.nabble.com/JBI-components-cannot-be-deployed-to-other-JBI-containers-tp14948242s12049p14948242.html Sent from the ServiceMix - User mailing list archive at Nabble.com.
