Camel -> Activiti -> Camel

[castyn]

Hello all, I am new here so be gentle. 

I am at the design phase of a project where we'll be integrating existing services with activiti, and we are using camel + servicemix for the ESB component.  I see from reading documentation that camel has activiti as a feature, and that Activiti has camel as a component.  My question is, would I need both Activiti as a standalone and Camel/Servicemix with the activiti component enabled to integrate the two, or can I effectively embed Activiti within camel using the feature?

[trademak]

I'm not aware of an embedded Activiti in Camel. We do support an embedded Camel container in Activiti though. So that would be my choice of weapon.

Best regards,

[castyn]

I should have clarified, servicemix not just Camel.  Servicemix has features that can be installed for camel-activiti, which natively loads the activiti engine into servicemix and exposes activiti endpoints for use in camel.  In my use case Activiti is more of a small part of a larger ESB where we want to leverage some of that functionality into already existing integration with REST APIs of services, database, etc.

[smirzai]

Hi Castyn,
I guess you are talking about activiti component in ServiceMix as mentioned in http://camel.apache.org/components.html
That component is also provided by Activiti team. Both sides are actually the same thing.

If you have libraries in the path and proper configuration, you can go from camel into Activiti and vice versa.
You can call it embedded, as the other component is called by jar files and not rest.