If I can recommend something - I would opt for something else than BPEL (and ODE). You can use camel-activiti (http://activiti.org) integration and call your services without WSDL / Web Service. In your case - if you have existing services - it's not big deal, but BPEL is weak on REST ground and even more weak if you want to use one way communication.
Best regards, Lukasz Dywicki -- Code-House http://code-house.org Wiadomość napisana przez Mariusz Brylant w dniu 11 kwi 2012, o godz. 14:14: > There are a number of differences. > > Apart from the obvious - such as that BPEL very much depends on XML and > associated technologies ) and ESBs do not have to speak XML at all (at least > the good ones) - the most important difference for me is that BPEL is > statefull. > > You can access messages associated with previous activities and at any point > in time the state of the process can be automatically serialised and later > restored BPEL implementations, including ODE give you that out of the box. > But be warned BPEL is very chatty because of its statefullness and as a > result tends to generate a lot of load on the DB. > > If you have a simple CBR (content based routing) or similar case, it makes > little sense to get bpel involved IMHO. > > Regards, > Mariusz > > > On 11 Apr 2012, at 12:44, johngalt wrote: > >> We have an integration (about 15 or so web services, mostly REST, some WSDL) >> that we are evaluating if servicemix can be used as the platform. We >> definitely need the ability to implement routing between these services. >> I've been playing around with some camel routes, which (at least initially) >> would seem to meet our needs. So, I'm a bit confused as to what additional >> abilities BPEL gives me that camel does not. Or why I would use one or the >> other / some combination of the two? >> >> Any words of wisdom? >> >> Regards >> >> -- >> View this message in context: >> http://servicemix.396122.n5.nabble.com/Camel-vs-BPEL-ODE-tp5632572p5632572.html >> Sent from the ServiceMix - User mailing list archive at Nabble.com. >
