Life and Death Workflow with JBoss jBPM
From Kb
Contact Article Author | Blog of Article Author | FirstPartners.net Home | LinkedIn profile of Author
Contents |
See Also
BPEL - Business Process Execution Language
- Hides Engine
- People interact with end points (Web Services / SOA). Similar to Web Forms example , except that it is machines rather than people kicking the flow to the next stage in the process.
- While it is only capable of calling web services right now, there are plans to use Apache WSIF [1]
Use BPEL instead of JBoss jPDL (note were are reference to the process definition language) if ..
- message exchange with efficiency (no Java/XML binding) and type safety (automatic format checking)
• comfortable message content manipulation (XPath 1.0 expressions) • asynchronous message reception • encapsulation of the underlying web services machinery
- BPEL is near industry standard language , while jPDL is specific to JBoss (but visual worklow means that it is instantly understood)
Chap 3 Getting and Installing jBPM BPEL and Examples
- Separate Download
- Don't need JBoss App Server (but it is where the workflow is tested most, and where the out-of-the-box samples are located).
- Deployed as SAR file (JBoss Service Archive , so much easier to go with the flow)
- BPEL contains jBPM persistence (to Hypersonic??)
- Can deploy via web console or Ant script
- May need to override standard Java XML Libs with those from Apache
