Three major mainstream workflow engine technology analysis and market prediction 1. From "Kung Fu" to see me, I will think that it is a full old antique, this is not, "Kung Fu", I will see it in February this year. However, I have seen "Kung Fu", I think more than a general person: Zhou Xingxing Warter Rivers, and his fat big brother goes out to knock on the bamboo pole, why do you want his big brother's chest to paint two ax? Find a false mountain! The talent that is equipped is not bullied.
This reminds me of the year before: JBPM JOINS JBOSS AND BECOMES JBOSS-JBPM. That is, JBPM found a riser JBoss, so I didn't have to wander outside.
Ok, we turn into the topic, talk about the three mainstream open source workflow engines that say here: Shark, OsWorkflow, JBPM.
Shark's mountain is enhydra. What did ENHYDRA do? too much! From the J2EE application server, to the O / R mapping tool, to this workflow engine, etc. Why is Shark's persistence layer to implement DODS? It is because they are a family.
JBPM is the mountain is JBoss. The persistence of JBPM3 is implemented with Hibernate3, it is because of this reason. JBPM3's graphical process definition has decided to embed JBoss Eclipse IDE, let's take a look at the JBoss Eclipse IDE Preview 1.5 version, we have already edited a JBPM3 process definition file with plug-in.
The mountains of OsWorkflow are Opensymphony. I really like this organization, it made a lot of good things. When developing a workflow management system, I recommend it with another thing: WebWork2. The Open Source Workflow Engine, presided over, is implemented based on the WW2 Spring Hibernate architecture.
When you say this paragraph, you say that all J2EE application servers have their own workflow engine, as mentioned above, enhydra, jboss, and WebSphere and WebLogic, which are not mentioned, visible, learn workflow engine Technology is indeed very important.
2. If you are in the mountains, you can't do it. Zhou Xingxing joined the ax to fight the head of the evil god? To save yourself, still have to rely on the palm.
Shark's process definition language is XPDL, we know that the two most important concepts of XPDL are Process and Activity. The Activity in XPDL is the concept of activity graph in UML1.x. The activity map is suitable for workflow modeling. It is easy to perform bifurcation control with respect to the status map, which can be performed in order to execute simultaneously, and one has an advantage of there is a lane The concept can control the production of tasks in the workflow engine. Shark's 神 神 is the activity map.
What is OSWORKFLOW? We know that it has an important concept is State ... Oh, we know, it's like the palm of the palm. I don't know what fsm is? ? Then you are reading a college, it is definitely not a good student; of course, I don't know if you don't tighten it. You can understand him as a status map. State in OSWORKFLOW is expressed by Step and Status. One state is a STATUS in a Step; and the STATE conversion is driven by Action, and the event in the status map is because an Event corresponds to an action.
JBPM is like the palm of the palm, it is simple to apply the status map active map petrinet, and the activity map is still UML2.0. In the active map of UML2.0, the node is not called an activity (Action), and the activity is a high-level concept that contains a sequence of action. A active map shows a series of actions that form an activity. JBPM also renamed Action, called State. The concept of the status map used by JBPM is transition / event, etc., you will go see it. JBPM has a concept of Petrinet in an internal implementation, such as Token, Signal, etc. what? I don't know what PETRINET is? So your college is learning computer? Not? Then you may be learning textbooks, learning machinery / electrical / civilian engineering / transportation and other majors have a course in contacting Petrinet. If you haven't learned, look at JBPM, anyway, we don't engage in theory, know the general concept. 3. Market forecasting is a thing that is difficult to eat. A lot of foreign masters do the forecasts to be embarrassing ... Fortunately, I have predicted the prediction in "Workflow" last year. At that time, my forecast was: Shark ... will be boarded the number one throne. It should be said that before that article published, the domestic workflow engine usage rate is OsWorkflow; at the end of last year, Shark has a significant advantage, I analyzed the following:
1) Domestic enterprises look at XPDL, because this means that in the product manual, you can blow it "" We follow WFMC ... "
2) Because I sincerely "SHARK Workflow Engine Main Promoters in China", most of the friends who give me feedback workflow management system development and selection techniques are useless Shark
3) SHARK is indeed a good workflow engine, even if you just want to learn XPDL, you can also start from learning Shark.
It has now reached the era of "Workflow's Workflow" to the era of the feudal society to capitalism, and driven this transformation, not someone else, is the JBPM mentioned above. JBPM3 will release the Alba version in March, and the final version of JBPM3 will support the core part of BPEL4WS. So, I estimate that Shark will take the first throne by JBPM3 after hundreds of days of leading the wind. The author's open source agility Workflow Development Framework AgileFlow will integrate JBPM3 while supporting the Agile Engine and JBPM3 Engine.
But is BPEL4WS really touching us so fast? No. I estimate that it wouldn't really walk into our lives this year. When will it be? This will be the content of my next article to predict, I can't tell now, what I think is, is it to be self-sufficient, "JBPM3 Workflow Engine is the main promoter in China", huh.
