jBPM Developer Guide Review
One Minute Bottom Line
|This book provides a comfortable way to learn and work with jBPM and jPDL. It gives you a better idea of how to apply BPM in your future projects. The content offers a solid basis for beginners in jBPM.|
This is an interesting read by Mauricio Salatino that teaches you jBPM from the scratch and shows you how to get your hands dirty with this powerful tool!What you will learn from this book :
Here's what the table of contents looks like:
- Chapter 01: Why Developers Need BPM
- Chapter 02: jBPM for Developers
- Chapter 03: Setting Up Our Tools
- Chapter 04: jPDL Language
- Chapter 05: Getting Your Hands Dirty with jPDL
- Chapter 06: Persistence
- Chapter 07: Human Tasks
- Chapter 08: Persistence and Human Tasks in the Real World
- Chapter 09: Handling Information
- Chapter 10: Going Deeply into the Advanced Features of jPDL
- Chapter 11: Advanced Topics in Practice
- Chapter 12: Going Enterprise
What I liked:
- There are many valuable images that are an excellent complement to the author's explanations.
- The author explains his theory well and gives an introduction to many important terms.
- All the nodes are used in GDP.
- The explanaion on why one should use jBPM is excellent. It includeshow to work with other Java tools like maven and Eclipse.
- There are case studies available.
- The author often starts with a simple diagram (GPD) for a process and then transforms it into a more realistic process using valuable nodes and simple jDPL code.
What I disliked:
- There was a lot of snippet code included where I would have preferred complete code.
- Output results were not shown.
- The book is based on jBPM version 3.2.6 SP1, but the current version is 4.3
How to improve:
The main thing that can be done to improve this book is to include complete code rather than snippet code.Click here to purchase this book.
If you want to see more details on the summaries of each chapter in this book, read my longer review.
(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)