Skip to content
This repository was archived by the owner on May 12, 2021. It is now read-only.

apache/ode

Folders and files

NameName
Last commit message
Last commit date

Latest commit

a0c2d1a · Jan 14, 2020
Dec 2, 2010
Dec 2, 2010
Apr 29, 2018
Jan 29, 2018
Dec 2, 2010
Apr 28, 2018
Apr 28, 2018
Dec 2, 2010
Jun 28, 2017
Jan 29, 2018
Dec 8, 2010
May 4, 2018
Jan 29, 2018
Dec 2, 2010
Apr 28, 2018
Apr 28, 2018
Jun 28, 2017
Aug 29, 2013
Nov 29, 2017
Apr 28, 2018
Nov 26, 2015
Nov 28, 2017
Nov 28, 2017
Nov 28, 2017
Nov 28, 2017
Jun 28, 2017
Jan 7, 2011
Nov 26, 2015
Feb 15, 2011
Aug 26, 2013
Nov 29, 2017
Jun 9, 2015
May 27, 2010
Nov 26, 2015
Nov 28, 2017
Jun 28, 2017
Nov 28, 2017
Nov 28, 2017
Jun 28, 2017
Nov 26, 2015
Nov 29, 2017
Apr 28, 2018
Jul 22, 2014
Jan 12, 2011
Jan 30, 2018
May 27, 2010
Aug 2, 2007
May 27, 2010
Apr 4, 2011
Apr 28, 2018
Jan 12, 2011
Apr 28, 2018
Nov 28, 2017
Dec 20, 2017
Jan 14, 2020
Jun 7, 2015
Jun 17, 2014
May 27, 2010
==============
  Apache ODE
==============

Apache ODE is a WS-BPEL compliant web services orchestration engine.
It organizes web services calls following a process description
written in BPEL. Another way to describe it would be a web service
capable workflow engine.

For more information check the following resources:

 * Our web site: http://ode.apache.org/
 * The WS-BPEL 2.0 technical committee webinars linked here:
     http://ode.apache.org/introduction.html

Apache ODE is an open source project, as such we welcome all your
help and contributions. To participate and get involved, our mailing
lists are the best resources to start from:

    http://ode.apache.org/mailing-lists.html

Finally here is a non exhaustive but representative features list:

 * Compliant with both BPEL4WS 1.1 and WS-BPEL 2.0.
 * Deploys both as a WAR in any web container (using an Axis2-based
 communication layer) or as a JBI service assembly.
 * Small footprint server suitable for experimentation or 
 single-server production use.
 * Compiled approach to BPEL that provides detailed analysis and 
 validation at the command line or at deployment.
 * Processes hot deployment and management web service interface (war
 deployment only).
 * High level API to the engine that allows you to integrate the core
 with virtually any communication layer or even embed it.