Uhm.... my personal comments - .NET 3.5 is stable, just like jBPM 3.2.3 is stable... or JDK 1.5.0_02 is stable. If you would have said .NET is stable, then it is a different thing (4 releases in?). The jBPM API has not changed that much in the last 2 years, so I'd say it is quite stable.
>From your statement I cannot determine where persistence and thread >synchronization (aren't they two only partly related things?) are more robust >in MS Workflow then in jBPM. The latter uses Hibernate which is really robust. >The relation with Rich Clients is totally unclear to me, since jBPM can be >used in stand-alone, pure web or rich client implementations. If you could >elaborate a little more, I can try to comment. Comparing the MS Workflow 'platform' to jBPM is imo comparing apples to grapes (not even oranges). I think you should include SEAM, JBossTools etc... to have a real comparison (I do not know the details of MS Workflow) So even with my basic knowledge of MS Workflow, I have to say you statement of 'superiour' is a bold statement and needs more detailed arguments (yes, I'm biased, but I get the feeling you are to ;-) ) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4166022#4166022 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4166022 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
