JBPM 和 BPEL/ESB 之间的区别
JBPM 和 BPEL（和 ESB）有什么区别？ 您能解释一下吗？
RGDS
what is difference between JBPM and BPEL(and ESB)?
Would you please explain them?
RGDS
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（4）
我对JBPM不太熟悉。但这似乎是一个业务工作流程，可以与 java 服务或基本上基于 java 的流程一起使用。不仅仅是网络服务。
BPEL 是编写 Web 服务工作所遵循的标准。始终使用 BPEL 语言来集成 Web 服务并基于此定义流程。这是我为此编写的示例[1]。
ESB 主要用于中介和转换消息。当您集成不同类型的系统时，它们之间的消息流可能会有所不同。所以人们可以使用 ESB 作为中介。一些 ESB 也提供服务集成。 WSO2 ESB[2] 就是这样一个您可以使用的 ESB。
[1] http://wso2.org/library/articles/ 2011/05/integrate-business-rules-bpel
[2] http://wso2.org/library/esb
I am not much familiar with JBPM. But it seems to be a Business work flow which can work with java services or basically java based process. Not only with web services.
BPEL is a standard to write work follows with web services. Always BPEL language used to integrate the web services and define processes based on that. Here is an sample I have written for that[1].
ESB is primarily used for mediation and transform messages. When you integrate different types of systems, the message flow between them may vary. So people can use ESB as a mediator. And also some ESBs provides service integration as well. WSO2 ESB[2] is such an ESB you can use.
[1] http://wso2.org/library/articles/2011/05/integrate-business-rules-bpel
[2] http://wso2.org/library/esb
确切地说，ESB + BPEL 是一个集成问题的技术解决方案。如果您只想使用 jBPM5 进行集成，那没问题，您可能会使用带有 ESB 的 jBPM5 来进行消息的所有中介和转换。 BPMN2 是一种描述业务流程的标准符号，它的强大功能将帮助您描述更多高级/面向业务的场景，而不仅仅是简单的系统集成。人机交互的概念深深嵌入到语言和 jBPM5 基础设施中。考虑一下这样一个事实：您的模型（业务流程）可以由业务/非技术人员共享和理解，并且当业务现实发生变化时，他们将能够验证、改进和更改这些定义。
希望有帮助！
Exactly, ESB + BPEL is a technical solution for an integration problem. If you want to use jBPM5 just to do integrations thats fine and you probably will use jBPM5 with an ESB for all your mediation and transformation of your messages. The power of BPMN2, a standard notation to describe business processes will help you to describe more high level/business oriented scenarios than just simple system integrations. The concept of human interaction is heavily embedded in the language and in the jBPM5 infrastructure. Think about the fact that your models (business processes) can be shared and understood by business/non technical people and they will be able to validate, improve and change those definitions when the business reality changes.
Hope it helps!
jBPM 基于 BPMN。这是一个基于 Java 的解决方案，可解决您的工作流程问题。
BPEL 也解决了工作流问题，但方法完全不同。它是基于网络服务的。
从语法角度来看，BPEL 比 BPMN 更复杂，但被认为更广泛。
我想，正确的比较实际上应该是 BPMN 和 BPEL 之间。
jBPM is BPMN based. This is a java based solution to your workflow problem.
BPEL is also solves the workflow problem, but the approach is entirely different. It is web service based.
BPEL from a syntax perspective is more complex than BPMN but is considered more extensive.
The right comparison should actually be between BPMN and BPEL I guess.
相似之处
技术方面的编排差异。
BPM 只能在存在人工任务的情况下使用，否则 ESB 可以完成从编排到转换、规则到 CEP 的所有工作
Similarity
difference in terms of technology.
BPM should only be used where there is a human task otherwise ESB fulfills everything from orchestration to transformation to Rules to CEP