BPEL4People Virtual Roundtable Interview
- Share
-
- |
Read later
My Reading List
In this interview, held at the time of the first OASIS BPEL4People technical meeting, InfoQ spoke with several of the authors of the BPEL4People and WS-HumanTask specifications. We asked them about the history of the specifications, how they see them fitting within BPM and whether they will divide the community as much as BPEL has so far.
1 comment
Community comments
Alternative BPEL4People implementation
by
Modrzyk Nicolas
Posted
Alternative BPEL4People implementation
by
Modrzyk Nicolas
Intalio is also supporting the efforts put into the BPEL4People specifications.
The Tempo project follows the BPEL4People architecture to provide all the necessary workflow functions. At this time, Tempo does not rely on any BPEL extensions and uses fully interoperable WSDL and REST interfaces as its core APIs. Over time, we intend to implement the full BPEL4People specification.
The Tempo project follows the BPEL4People architecture to provide all the necessary workflow functions. At this time, Tempo does not rely on any BPEL extensions and uses fully interoperable WSDL and REST interfaces as its core APIs. Over time, we intend to implement the full BPEL4People specification.
Educational Content
Writing Usable APIs in Practice
Giovanni Asproni May 19, 2013
Concurrency in Clojure
Stuart Halloway May 17, 2013
Hello stranger!
You need to Register an InfoQ account or Login to post comments. But there's so much more behind being registered.Get the most out of the InfoQ experience.
Tell us what you think