Through nearly 1 months of efforts, the successful packaging completed Openwebflow and open source to GitHub, please have the necessary peer consultation fee!
Openwebflow is a Activiti-based workflow engine that does some peripheral packaging work for workflows in a Web environment.
Activiti users may feel that there are some areas for improvement:
- Activiti provides a demo for Web applications, but the demo kidnapped a lot of things (such as: the definition of a form to follow its shape, its own business logic is nowhere to be inserted, etc.);
- Activiti API is very complex (in fact, it is not complicated, on the contrary, its design is very clear, is to find a bit of trouble), it is best to have some quick-use tool classes;
- Activiti kidnapped the user information sheet design! This is really deadly, because almost every business system will belong to its own user information structure (including user/group/membership), but it is not necessarily stored in activiti like the library, the structure of the table is not necessarily the same, sometimes, Some information (such as dynamic Group) is not used to store the table at all;
- The process model allows you to specify the execution permissions for each activity, and Activiti support is also great. However, the business system may need to dynamically set execution permissions for these tasks (e.g. dynamic group) according to the actual situation;
Openwebflow has done some work for the above requirements. In simple terms, the Openwebflow framework:
- Provides a series of tool tools that you can use in Java applications and even in the methods of your own controller, see tool classes;
- Wrapping up a series of events, note that these events are web contexts (unlike Activiti's event mechanism), and developers can write their own EventHandler based on the event mechanism, and it's convenient to EventHandler the notation of the spring Controller of the same method (support parameter Auto-mapping), see Openwebflow event mechanism;
- Stripping the activity of the rights management, to achieve a decoupling from the process definition, that is, the user to the activity of the access control information separately managed (rather than in the process definition of pre-written dead), so as to facilitate the dynamic adjustment of permissions, see the Custom activity Rights management;
- Stripped of the User Information table Unified Management! Client program can forget Activiti user table, Group table, member relationship table, see Custom user member Relationship management;
Developer Use Help: Https://github.com/bluejoe2008/openwebflow/wiki
Thanks to the coffee rabbit http://www.kafeitu.me/, there is a lot of discussion about the Activiti application program.
Absolutely original, support the Chinese open source!
Activiti-based open source Workflow engine extension Framework--openwebflow
