Camel vs. osworkflow

[Lou Parisi <Lo...@photomask.com>]

I was wondering if anyone could give me the use case/scenario where you would
select osworkflow for executing a workflow in servicemix vs. using either
static or dynamic routes with camel.  It seems Camel is well integrated with
servicemix and provides a significant amount of functionality so I would
think camel is the standard.  Assuming that is true, when would one choose
osworkflow over camel?

I am considering an application that requires a workflow to execute several
applications in sequence.  I would wrap the existing applications as
services in servicemix.  

Thanks for any comments/opinions.  Lou
-- 
View this message in context: http://www.nabble.com/Camel-vs.-osworkflow-tp24686462p24686462.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.

Re: Camel vs. osworkflow

[Lou Parisi <Lo...@photomask.com>]

JB,
Thank you for your explanation.  I was thinking mostly the same as you but
wanted to get some additional feedback.  I agree that certainly Camel does
not have the ability to maintain state so this is an obvious use case.  The
other use case you mention is condition, loop, etc.  I guess I could imagine
that some amount of this can be implemented in camel using content-based
routing assuming the message content is updated based on the last step.  I
guess the decision point is based on how complicated are the conditions and
looping for the workflow.  Perhaps it is easier to do very complicated
conditions and loops in osworkflow vs. camel.

Best regards, Lou


Jean-Baptiste Onofré wrote:
> 
> 
> Nevertheless, only Camel isn't a workflow engine and so give a limited 
> answer to design a real business workflow.
> Typically, a workflow engine use a database backend to maintain state 
> between each workflow steps. Using a workflow engine, you can define 
> condition, loop etc between each workflow stage.
> In fact Camel can be use in some workflow steps but can't manage the 
> whole workflow alone.
> 
> 

-- 
View this message in context: http://www.nabble.com/Camel-vs.-osworkflow-tp24686462p24687167.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.

Re: Camel vs. osworkflow

[Jean-Baptiste Onofré <jb...@nanthrax.net>]

Hi Lou,

Camel is a great tool to solve a lot of integration problem. It allows 
us to easily implement EIP (Enterprise Integration Pattern). Basicly, 
Camel is the "SMX standard" when you need to implement advanced routing 
(content routing, multi recipient, etc), transformation (for example 
using velocity templating language) and filter (content filter, etc).
Nevertheless, only Camel isn't a workflow engine and so give a limited 
answer to design a real business workflow.
Typically, a workflow engine use a database backend to maintain state 
between each workflow steps. Using a workflow engine, you can define 
condition, loop etc between each workflow stage.
In fact Camel can be use in some workflow steps but can't manage the 
whole workflow alone.
If I need to compare osworkflow to another tool it would be ODE. In fact 
ODE is BPEL engine and using BPEL (Business Process Execution Language) 
you can describe a workflow.

I hope that I was clear :)

Regards
JB

Lou Parisi wrote:
> I was wondering if anyone could give me the use case/scenario where you would
> select osworkflow for executing a workflow in servicemix vs. using either
> static or dynamic routes with camel.  It seems Camel is well integrated with
> servicemix and provides a significant amount of functionality so I would
> think camel is the standard.  Assuming that is true, when would one choose
> osworkflow over camel?
> 
> I am considering an application that requires a workflow to execute several
> applications in sequence.  I would wrap the existing applications as
> services in servicemix.  
> 
> Thanks for any comments/opinions.  Lou

-- 
Jean-Baptiste Onofré
---------------------------------
  HomePage
http://www.nanthrax.net
---------------------------------
  Contacts
jbonofre@apache.org
jb@nanthrax.net
---------------------------------
  OpenSource
BuildProcess/AutoDeploy
http://buildprocess.sourceforge.net
Apache ServiceMix
http://servicemix.apache.org
-----------------------------------
PGP : 17D4F086