Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
-
Patch Available
Description
Current servicemix-camel component has a short coming of sharing the camel context in the servicemix-camel component.
It can't create a right camel endpoint for servicemix if there are more than 2 servicemix-camel SU deployed in the container. We need to support looking up the camel-context with the SU name in servicemix-camel component.
So we need to refactor the servicemix-camel code to pull the camel-jbi component out of servicemix-camel component and make sure there is a new camel-jbi component per camel context ( or per SU).
In this way the servicemix-camel SU developer could also do some customization of the camel-jbi component per camel context, and the JbiBinding could not be annoying thing for servicemix-camel component.