Hello,
I have been reading JPDL documentation and realized that we can add our custom implantation java classes to handle workflows according to some business requirements
We achieve such customization by implementing
- Custom actions by implanting ActionHandler interface
- Decision handlers by implementing DecisionHandler interface
- Task assignment handlers by extending AssignmentHandler interface
- Event listeners by extending EventListener interface
- Custom external activity behavior by extending ExternalActivityBehaviour interface
- User defined java classes and scripts by using java and script JPDL tags
This can save lots of time and effort to develop a definition language and parser
I attached a file, that I got from JBPM documentationm, that contains examples on how to use the above listed handlers
- So can we use the above interfaces and implement them to have classes that behave according to our business needs?
- Is there a limitation to what extent we can control JPDL actions, decision, tasks, events, and activities behavior ?