I have been studying workflow from reading, I have been for several years, but I've studying Shark, I have been more than a year, I think about it, still make a small progress.
At the beginning, China's research on Shark was basically blank. At that time, everyone was talking about Obe, OSWORKFLOW, OFBIZ ... After a few Shark articles in the 9CBS document center, May 2004, in "Workflow E "Apply for the establishment of Shark Technology, we finally have its own space .....
Due to the complexity of Shark, I accelerated the development of AgileFlow and released a version 0.8 in September. As the foundation of learning Shark and understanding the workflow concept, I can't think of a good response, friends who come to email are more and more many....
<< Large situation in Workflow >> After the publication, Shark and AgileFlow were more obvious, and some friends used Shark and AgileFlow to make two business process instances, send them to my mailbox to discuss workflow mail. The actions exceeded 2000 seals; I must have no way to reply, I can't help everyone ....
Now learn Shark friends, there are many new articles about Shark in the 9CBS blog. From the mail I received, the number of users who currently study in China should be Shark> OsWorkflow> JBPM, of course, I There is no way to statistically apply to the proportion of workflow engines for the process system
Perhaps because of my propaganda, perhaps due to the Jawe's brother relationship, maybe due to completely follow XPDL, Shark is currently pushed to the boss; however, it is indeed a lot of shortcomings: complex, performance, and persistence DODS ...
I hope these shortcomings are not fatal.
