The fifth chapter of "Workflow Star" is written in these two days, and the Workflow Pattern of the Aalst Master is readily read.
I have a marble carvings, which carved a "warmth and knows new". It seems that it is a primary school. Of course, it is still in his hometown. I don't know if it is still, but always in that sentence. Stay in the mind - the philosophy of the ancients is always right (haha, this is some nonsense). Rereading Workflow Pattern, there is indeed a different gain, and there is always a lot of benefits.
Like WP, this is not read for a few times, it is not enough to understand its true meaning. Of course, if it is not practical, it is also white. At this time, I have to admire the enthusiasm of the first people - theory and practice, practice is the only standard for inspection. ·····
Workflow Pattern is a very abstract layer. It cannot be classified in the J2EE in Design Pattern. I have so much ratio in the early days, but it is now not thinking. DP has been realized in norming your achievement and basic implementation class. WP is not much practical paradigm constraint on Workflow, which is just an abstract description of the operating mode during Workflow operation. That is, you can use any implementation to implement the scene described in each mode. For example, Deferred Choice is folded in a workflow mode, you can use the PN mechanism to implement, or you can implement it with a hard code.
Moreover, the mode described in WP is allowed to "combine", and the combination of these modes can be used to express more complex flow running scenarios. If you are elaborating with now, you can say that Workflow Pattern does what is done to find the minimum model element of the process running scene.
