A lot can be read in the Toms' blogs
So to be short, jpdl will not be replaced by bpel, but if bpel will be extended like oracle and bea did, that should be answered by someone from JBoss (most likely Alex)
btw, jbpm already has a nice 'core' on which both languages are implemented. 'Graph Oriented Programming' is the keyword for this.
Some extension points I have envisioned are:
Attach action handlers to events of the generated jBPM process graph
Incorporate Apache WSIF for direct Java EE integration
Create an extension activity for human tasks which leverages the jBPM task management facilities.
Thanks, I think that sounds quite good.. Another question is a migration between existing JPDL-Process-Definitions into BPEL-Definitions.
Maybe this is will be a problem, JPDL is a large & powerfull language while BPEL is limited and doesn´t know about Java-Actions, Timers etc.
We´ll see, in worst case we have to translate the definitions by hand..
Thanks for the infos!!
or don't migrate at all. We use both (jpdl for workflow and bpel as it is for orchestration). The WSIF otoh is nice to have
exactly. the whole point of supporting multiple process languages is not having to migrate. workflow and orchestration are very different domains and should be addressed with the appropiate language.
Side note: BPEL has timers! See the wait activity and onAlarm entries in event handlers and pick structures.