forked from apache/ode
-
Notifications
You must be signed in to change notification settings - Fork 3
/
README
44 lines (31 loc) · 1.59 KB
/
README
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
# 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.
## Docker
### Build image on M1 Processor
Clone the repo https://github.com/sathwik/docker-buildr go to the folder `jruby-jdk8` build the image with:
`docker build -t sathwik/apache-buildr:latest-jruby-jdk8 .`
Go to the ODE folder and build the image with:
`docker build -t opentosca/ode:latest .`