Drools Flow is the best workflow solution that I came across recently. It has a luxury to be better than other solutions, since it is built and designed recently, and based on lessons learned from other long existing, somewhat over engineered frameworks.
Drools Flow comes as a community project along with an official Drools 5 release that besides Flow includes: Guvnor, Expert and Fusion.
Unfortunately Drools Flow does not have an official Red Hat support contract yet, and that is a stopper for some big corporations to consider it. One might think the support is not there for political reasons due to the jBPM project living under same support roof.
It depends what kind of initial investment you want to make. jBPM is the best in terms of features and flexibility, but OSWorkflow is a more lightweight, easier to get up and running and has with a smaller learning curve.
I'll cast a vote for jBPM. We used it on a larg-ish ETL platform in-house and it seemed to work quite well. I don't have anything to compare it to, however.
发布评论
评论（5）
Drools Flow 是我最近遇到的最好的工作流程解决方案。 它比其他解决方案更好，因为它是最近构建和设计的，并且基于从其他长期存在的、有些过度设计的框架中吸取的经验教训。
Drools Flow 作为一个社区项目与官方 Drools 5 发布除了 Flow 之外还包括：Guvnor、Expert 和 Fusion。
不幸的是，Drools Flow 还没有正式的红帽支持合同，这阻碍了一些大公司考虑它。 人们可能会认为，由于 jBPM 项目处于同一支持范围内，因此出于政治原因而没有提供支持。
Drools Flow is the best workflow solution that I came across recently. It has a luxury to be better than other solutions, since it is built and designed recently, and based on lessons learned from other long existing, somewhat over engineered frameworks.
Drools Flow comes as a community project along with an official Drools 5 release that besides Flow includes: Guvnor, Expert and Fusion.
Unfortunately Drools Flow does not have an official Red Hat support contract yet, and that is a stopper for some big corporations to consider it. One might think the support is not there for political reasons due to the jBPM project living under same support roof.
这取决于您想要进行什么样的初始投资。 jBPM 在功能和灵活性方面是最好的，但 OSWorkflow 更轻量级，更容易启动和运行，并且学习曲线更小。
It depends what kind of initial investment you want to make. jBPM is the best in terms of features and flexibility, but OSWorkflow is a more lightweight, easier to get up and running and has with a smaller learning curve.
这里有一篇文章比较了 kBPM、OpenWFE 和 EnHydra Shark，看起来它有一些好的、全面的信息。
Here's an article that compares kBPM, OpenWFE, and Enhydra Shark that looks like it has some good, thorough info.
YAWL - 另一种工作流程语言
http://en.wikipedia.org/wiki/YAWL
YAWL - Yet another workflow Language
http://en.wikipedia.org/wiki/YAWL
我将为 jBPM 投一票。 我们在一个大型的内部 ETL 平台上使用了它，它似乎运行得很好。 然而，我没有任何东西可以与之比较。
I'll cast a vote for jBPM. We used it on a larg-ish ETL platform in-house and it seemed to work quite well. I don't have anything to compare it to, however.