I'll complement Matthieu's answer. Ode's native architectural style is web services. We have integration layers for Axis2, JBI and SCA. Each of these provides multiple transport and binding options, such as SOAP/HTTP, plain XML/HTTP, JMS, POJOs, etc.
http://ws.apache.org/axis2/ http://servicemix.apache.org/components-list.html http://tuscany.apache.org/ We're also working on adding support for the REST architectural style. As a first step we made extensions to WSDL 1.1 to allow consuming a wider range of RESTful services: http://ode.apache.org/user-guide.html#UserGuide-HTTPBindingExtensionsforRESTfulservices The medium- to long-term plan is to support REST natively: http://ode.apache.org/restful-bpel-part-i.html http://ode.apache.org/restful-bpel-part-ii.html alex On Tue, Sep 23, 2008 at 7:51 AM, Matthieu Riou <[EMAIL PROTECTED]>wrote: > On Mon, Sep 22, 2008 at 10:44 PM, Denis Bessmertnyj < > [EMAIL PROTECTED]> wrote: > > > Hi Guys, > > > > Currenlty I investigate Ode for my BPEL taks and it is interesting does > Ode > > supports only WebServices or maybe other approaches also supported? > > > > BPEL is strongly tied to WSDL so ODE fits in a web services world. That > being said, we have different implementations of the ODE communication > layer > so in addition to Axis2 (pure Web Services) we also have JBI and SCA (see > in > Apache Tuscany). We're also working on an embeddable version that would > allow direct calls from say, Java, but it's still at a very early stage. > > Thanks, > Matthieu > > > > > > > > Thanks, > > >
