What Is It?

From JBoss’ web site:

JBoss jBPM is a powerful workflow and BPM engine that enables the creation of business processes that coordinate between people, applications and services. With its modular architecture, JBoss jBPM combines easy development of workflow applications with a flexible and scalable process engine. The JBoss jBPM process designer graphically represents the business process steps in order to facilitate a strong link between the business analyst and the technical developer.

Why Is It Interesting?

Many applications have the concept of an item of work that needs to be tracked: a sales order is started, and must be approved and filled; a customer complaint is opened and must be solved; etc.

jBPM provides a set of classes that model “business processes” and the “stages” that the processes are in. Different “tasks” can be be attached to various stages, as can “actions” (like send an e-mail, or fire off a web services request).

Instinctively, we tend to think of these processes as flow charts or series of boxes. And, conveniently, it is possible (but not required) to use a fancy-schmancy WYSIWYG editor to draw out the various stages/nodes and transitions between those nodes.

What Are Its Key Features?

External Links

  • Persisting Hibernate Objects as jBPM variables
  • Another link about persisting

Other Topics

  • Setting up jBPM’s jPDL Designer in Eclipse

It's only fair to share...
Share on Facebook
Tweet about this on Twitter
Share on LinkedIn

Leave a Reply