Hi guys,
  I feel basicly as same as Peterson. It seems like the jBPM 4.x won't be supported by jBoss, and the jBPM 5 is most likely replaced bye Drools Flow.
 
  If it is the dead end of jBPM 4, shall we have another way to continue fix issues for jBPM 4, because at this moment, here is a lot of project using jBPM 4 as their Process Engine.
 
2010-04-18

Xu Hui Sheng
WebSite: http://www.family168.com/

发件人: Peterson, Scott
发送时间: 2010-04-18  10:21:52
收件人: 'jbpm-dev@lists.jboss.org'
抄送:
主题: [jbpm-dev] jBPM 4.x dead end?

To me, jBPM 5 looks a lot more like Drools Flow than jBPM 4.x: for example, the vision includes WS-HT, integrated rules/events, and apparently no support for jpdl.  I think it’s a cool vision but it really does make jBPM 4.x look like a dead end that I should avoid.  Am I reading the tea leaves wrong? 

 

One suggestion is to go through the jBPM 4.4 and 4.x issues and decide which go in the “Won’t fix” category.  

 

Also, I’d like your opinion.  If I’m just starting out on a 12-18 month project, am I better off using Drools Flow instead of jBPM 4.x?  In which project will bugs get fixed and features get added?  Which project will make it easier to move to jBPM 5?

 

Thanks

Scott


-----Message Disclaimer-----

This e-mail message is intended only for the use of the individual or entity to which it is addressed, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If you are not the intended recipient, any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by reply email to Connect@principal.com and delete or destroy all copies of the original message and attachments thereto. Email sent to or from the Principal Financial Group or any of its member companies may be retained as required by law or regulation.

Nothing in this message is intended to constitute an Electronic signature for purposes of the Uniform Electronic Transactions Act (UETA) or the Electronic Signatures in Global and National Commerce Act ("E-Sign") unless a specific statement to the contrary is included in this message.

While this communication may be used to promote or market a transaction or an idea that is discussed in the publication, it is intended to provide general information about the subject matter covered and is provided with the understanding that The Principal is not rendering legal, accounting, or tax advice. It is not a marketed opinion and may not be used to avoid penalties under the Internal Revenue Code. You should consult with appropriate counsel or other advisors on all matters pertaining to legal, tax, or accounting obligations and requirements.