blocks|key|4193889|text|Activiti是一个有趣的项目，原因如下：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4193890|4193891|他们打算把引擎商品化。出于这个原因，他们使用Apache软件许可证。到目前为止，有几家公司在支持这个项目。“业务模型”有点类似于OpenStack使用的模型。|ordered-list-item|4193892|拥有一个BPMN2.0引擎是有意义的，它可以被所有人使用。这包括jBoss+(但我怀疑他们很快就会转换)。|4193893|4193894|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|L|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|M|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|N|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|P|8|@]|9|@]|A|$]]]|J|$]]

Activiti is an interesting project for several reasons:

<ol>
<li>They intend to commoditize the engine. For that reason they use the Apache Software License. So far several companies are backing that project. The "business model" is somewhat similar to that used by OpenStack.</li>
<li>It makes sense to have one BPMN 2.0 engine which is used and can be used by everybody. This does include jBoss (but I doubt that they will switch soon).</li>
</ol>

blocks|key|4194207|text|历史课：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4194208|jBPM和它的结果项目：|4194209|4194210|jBPM是在Redhat创建的，作为一个工作流引擎，遵循BPMN2.0+specification|ordered-list-item|offset|length|style|BOLD|4194211|Creators+of+jBPM，leave+jBPM项目和Redhat加入Alfresco。他们在那里创建了Activi。Activi的|4194212|创建者离开了Alfresco，开始了一个新的业务流程管理工具Flowable，它是从Activi派生出来的另一个业务流程管理工具。它们还遵循BPMN+2.0规范。他们有Zeebe，一个云原生业务流程管理，可以连接到Java，gRPC，Elasticsearch和Kubernetes。|4194213|4194214|非jBPM工作流/编排工具：|4194215|4194216|Uber+cadence|4194217|Apache+Airflow|4194218|Netflix+Conductor：微服务工作流编排引擎。|4194219|4194220|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/uber/cadence|1|https://en.wikipedia.org/wiki/Apache_Airflow|2|https://netflix.github.io/conductor/^0|0|0|0|0|4|0|1J|6|0|U|8|0|0|0|0|0|C|0|0|0|E|1|0|0|H|2|0|0^^$0|@$1|2|3|4|5|6|7|1C|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1D|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|1E|8|@]|9|@]|A|$]]|$1|E|3|F|5|G|7|1F|8|@$H|1G|I|1H|J|K]]|9|@]|A|$]]|$1|L|3|M|5|G|7|1I|8|@$H|1J|I|1K|J|K]]|9|@]|A|$]]|$1|N|3|O|5|G|7|1L|8|@$H|1M|I|1N|J|K]]|9|@]|A|$]]|$1|P|3|-4|5|6|7|1O|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|1P|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|1Q|8|@]|9|@]|A|$]]|$1|T|3|U|5|G|7|1R|8|@]|9|@$H|1S|I|1T|1|1U]]|A|$]]|$1|V|3|W|5|G|7|1V|8|@]|9|@$H|1W|I|1X|1|1Y]]|A|$]]|$1|X|3|Y|5|G|7|1Z|8|@]|9|@$H|20|I|21|1|22]]|A|$]]|$1|Z|3|-4|5|6|7|23|8|@]|9|@]|A|$]]|$1|10|3|-4|5|6|7|24|8|@]|9|@]|A|$]]]|11|$12|$5|13|14|15|A|$16|17]]|18|$5|13|14|15|A|$16|19]]|1A|$5|13|14|15|A|$16|1B]]]]

History Lesson:

jBPM and its resultant projects:

<ol>
<li>jBPM is created at Redhat as a workflow engine adhering to BPMN 2.0 specification</li>
<li>Creators of jBPM leave jBPM project and Redhat to join Alfresco. There they create, Activi. </li>
<li>Creators of Activi leave Alfresco and start a new BPM tool, Flowable, which is a fork from Activi.</li>
<li>Camunda is another BPM tool forked from Activi. They also adhere to BPMN 2.0 Specification. They have Zeebe, a cloud-native BPM with connectors to Java, gRPC, Elasticsearch and Kubernetes.</li>
</ol>

Non-jBPM workflow/orchestration tools:

<ol>
<li><a href="https://github.com/uber/cadence" rel="noreferrer">Uber cadence</a></li>
<li><a href="https://en.wikipedia.org/wiki/Apache_Airflow" rel="noreferrer">Apache Airflow</a></li>
<li><a href="https://netflix.github.io/conductor/" rel="noreferrer">Netflix Conductor</a> : Microservice workflow orchestration engine.</li>
</ol>

blocks|key|2785421|text|请查看jBPM+7：https://www.jbpm.org/learn/releases.html|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2785422|对jBPM的支持和开发肯定还在进行中！|2785423|(顺便说一句，jBPM也使用BPMN2.0)|2785424|entityMap|0|LINK|mutability|MUTABLE|url|https://www.jbpm.org/learn/releases.html^0|A|14|0|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]]|C|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@]|C|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|C|$]]]|I|$J|$5|K|L|M|C|$N|O]]]]

Please check out jBPM 7: <a href="https://www.jbpm.org/learn/releases.html" rel="nofollow noreferrer">https://www.jbpm.org/learn/releases.html</a>

Support for and development of jBPM is definitely still ongoing! 

(Btw, jBPM also uses BPMN 2.0)

blocks|key|2785551|text|jBPM和Activiti都是BPMN引擎，但将它们进行比较|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2785552|2785553|jBPM比Activiti+|unordered-list-item|2785554|更复杂与jBPM|2785555|相比，与Activiti集成非常容易|2785556|但jbpm仍处于开发阶段，活动也处于开发阶段。|2785557|无论你的需求是什么，一切都在jbpm中可用，它是非常好的BPM，但与Activity相比，它有点复杂，不是那么有成效。|2785558|因此，如果您还没有决定使用哪种bpm，我建议您使用Activity，因为与Activity集成要比JBPM容易得多，比如LDAP或Spring。|2785559|此外，由于社区提供了良好的用户指南和文档，您可以很容易地学习活动，但对于JBPM用户指南和文档来说，这两者都没有太大帮助。另外，开发人员指南也没有达到标准。|2785560|球在你的球场上，你必须做出决定。|2785561|万事如意。|2785562|检查此链接|2785563|http://www.mastertheboss.com/activiti-bpmn/jbpm-vs-activiti-which-to-choose|offset|length|2785564|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|0|0|0|0|0|0|0|0|0|0|0|23|0|0^^$0|@$1|2|3|4|5|6|7|18|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|19|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|1A|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|1B|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|1C|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|1D|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|1E|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|1F|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|1G|8|@]|9|@]|A|$]]|$1|R|3|S|5|6|7|1H|8|@]|9|@]|A|$]]|$1|T|3|U|5|6|7|1I|8|@]|9|@]|A|$]]|$1|V|3|W|5|6|7|1J|8|@]|9|@]|A|$]]|$1|X|3|Y|5|6|7|1K|8|@]|9|@$Z|1L|10|1M|1|1N]]|A|$]]|$1|11|3|-4|5|6|7|1O|8|@]|9|@]|A|$]]]|12|$13|$5|14|15|16|A|$17|Y]]]]

jBPM and Activiti Both are BPMN engines
But on Comparing both of them 

<ul>
<li>jBPM is more complex then Activiti</li>
<li>it is really easy to integrate with Activiti as compared to jBPM</li>
</ul>

but still jbpm is under development phase so is activity

Whatever is your requirement, everything is available in jbpm ,it is very good BPM but as compared to Activity it is bit complex and not so fruitful.

So if you are yet to decide which bpm I would suggest you to go for Activity because integration of anything with Activity say LDAP or Spring is preety easier as compared to JBPM.

Also you can easily learn Activity because of good userguide and documentation provided by community, but in case of JBPM userguide as well as documentation neither are so helpful. Also Developer guide book is also not up to the mark.

Well ball is in your court ,you have to take decision.

All the Best.

chk this Link 

<a href="http://www.mastertheboss.com/activiti-bpmn/jbpm-vs-activiti-which-to-choose" rel="nofollow">http://www.mastertheboss.com/activiti-bpmn/jbpm-vs-activiti-which-to-choose</a>

blocks|key|2785683|text|我从14年撤回了我之前的答案。从今天的角度来看，答案当然应该包括jBPM，Activiti，Flowable和Camunda。这是在寻找重要的基于BPMN2标准的开源工作流引擎时最终得到的选择。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2785684|jBPM仍然非常以Java为中心，感觉像是社区构建的老式开源产品，而且仍然缺乏产品管理。|2785685|Activiti贡献者的主要部分是lefts和forked以及Flowable。看起来Activiti的关注点是围绕着Alfresco和他们的DMS的需求。|2785686|如果你考虑与答案相关的谷歌趋势，目前看起来是这样的：https://trends.google.com/trends/explore?q=jBPM,Camunda,Activiti,Flowable|offset|length|2785687|​|2785688|📷|atomic|2785689|2785690|entityMap|0|LINK|mutability|MUTABLE|url|https://trends.google.com/trends/explore?q=jBPM,Camunda,Activiti,Flowable|1|IMAGE|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/d2d229567cbd4c3bec1c4dfc9aba17d3.png|imageAlt^0|0|0|0|Q|21|0|0|0|0|1|1|0|0^^$0|@$1|2|3|4|5|6|7|13|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|14|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|15|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|16|8|@]|9|@$H|17|I|18|1|19]]|A|$]]|$1|J|3|K|5|6|7|1A|8|@]|9|@]|A|$]]|$1|L|3|M|5|N|7|1B|8|@]|9|@$H|1C|I|1D|1|1E]]|A|$]]|$1|O|3|K|5|6|7|1F|8|@]|9|@]|A|$]]|$1|P|3|-4|5|6|7|1G|8|@]|9|@]|A|$]]]|Q|$R|$5|S|T|U|A|$V|W]]|X|$5|Y|T|Z|A|$10|11|12|-4]]]]

I withdrew my previous answer from '14. From today's perspective the answer should certainly include jBPM, Activiti, Flowable and Camunda. This is the selection one ends up with when looking for the significant BPMN2 standard-based open-source workflow engines.

IMHO, jBPM remains very Java-centric, feels like an old-school open-source product built by a community and still shows a lack of product management.

Major parts of the Activiti contributors lefts and forked Camunda and Flowable. It seems like Activiti's focus is around the needs of Alfresco and their DMS.

If you consider Google trends of relevance to the answer, it currently looks like this: <a href="https://trends.google.com/trends/explore?q=jBPM,Camunda,Activiti,Flowable" rel="nofollow noreferrer">https://trends.google.com/trends/explore?q=jBPM,Camunda,Activiti,Flowable</a>

<a href="https://i.stack.imgur.com/9qUZJ.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/9qUZJ.png" alt="src: https://trends.google.com/trends/explore?q=jBPM,Camunda,Activiti,Flowable"></a>

blocks|key|1654203|text|好吧，jBPM肯定不会消亡，尽管它与3.x和4.x版本有很大的不同。在这里，您可以阅读有关jBPM+and+Activiti干杯弗朗西斯科的更多信息|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1654204|entityMap|0|LINK|mutability|MUTABLE|url|http://www.mastertheboss.com/jbpm/300-jbpm-vs-activiti.html^0|19|H|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

Well jBPM is surely not dying although there's a strong departure from the 3.x and 4.x releases. here, you can read more about <a href="http://www.mastertheboss.com/jbpm/300-jbpm-vs-activiti.html" rel="nofollow">jBPM and Activiti</a>
Cheers
Francesco

blocks|key|4193944|text|据我所知，jBPM+5是刚被重命名的drools+flow。所以它一开始是作为drools业务规则引擎的一部分，现在是jBPM+4的继任者。所以我认为jBPM项目负责人转移到活动中并不重要。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4193945|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

As I understand it, jBPM 5 is drools flow which just got renamed.
So it started as being part of the drools business rules engine,and is now the
successor of jBPM 4. So i dont think it really matters that the jBPM project lead moved to activiti...

blocks|key|1658145|text|传统上，jBPM有一个很大的缺点:可用性。一直非常强大，但最难使用和集成，这是Activiti流行和jBPM使用率下降的主要原因。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1658146|然而，今年随着新版本6的推出以及Wira平台(+http://www.a1.io/a1io_blog/wira-for-jbpm/+)的发布，jBPM卷土重来，它提供了一个非常好的jBPM执行框架。|offset|length|1658147|entityMap|0|LINK|mutability|MUTABLE|url|http://www.a1.io/a1io_blog/wira-for-jbpm/^0|0|O|15|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@$D|P|E|Q|1|R]]|A|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|M]]]]

jBPM has traditionally had one big drawback; usability. Has always been very powerful, but the hardest to use and integrate with, a major reason in Activiti's popularity and jBPMs decline in usage.

However, this year sees the resurgence of jBPM with the new Version 6 rolled out as well as the release of the Wira platform ( <a href="http://www.a1.io/a1io_blog/wira-for-jbpm/" rel="nofollow">http://www.a1.io/a1io_blog/wira-for-jbpm/</a> )that provides a really good jBPM execution framework.

blocks|key|4194257|text|不，jBPM不会消亡，但最近出现了更简单、更轻量级的BPMN版本，如Camunda、Flowable、Activiti和list等。jBPM是这场竞赛中的老玩家之一，与其他工具相比，在创新、新功能、复杂性、部署、支持、稳定性、社区等方面肯定会输给竞争对手。另外，redhat+PAM是另一个原因，它可以比目前的BPM领导者，如Pega，IBM+BPM等便宜10倍的价格购买。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4194258|归根结底-+jBPM不会消亡，它会得到支持。|4194259|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

No, jBPM is not dying but more simpler and lightweight versions of BPMN are coming out recent days like Camunda, Flowable, Activiti and list goes on. jBPM is one of the old player in the race and certainly loosing to competition in terms of innovations, new features, complexity, deployment, support, stability, community etc. etc. compared to these other tool. Also redhat PAM is another reason which can be purchased with 10X cheaper price than current BPM leaders like Pega, IBM BPM etc.
Bottom the line - jBPM is not dying and will get support.

I have heard that the developers of "jBPM" have transferred to "Activiti BPMN 2" in recent times (ex: Tom).

I am wondering about is whether the support for jBPM will be over or not.. Besides, I would be glad to hear your ideas about if the improvements of Activiti BPMN will make it better or useful than jBPM as time goes on?

I would also like to know what are the pros/cons between them.

Is jBPM dying? What is the future of jBPM and Activiti BPMN?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我听说最近"jBPM“的开发人员转移到了"Activiti BPMN2”(例如: Tom)。我想知道的是，对jBPM的支持是否会结束。此外，我很高兴听到您关于Activiti BPMN的改进是否会使其随着时间的推移而比jBPM更好或更有用的想法？我还想知道它们之间的优缺点是什么。

问jBPM要死了吗？jBPM和Activiti BPMN的未来是什么？
EN

回答 9

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问jBPM要死了吗？jBPM和Activiti BPMN的未来是什么？EN

回答 9

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问jBPM要死了吗？jBPM和Activiti BPMN的未来是什么？
EN