Salaboy,como va, yo volviendo por estos lados, lucadnho contra el Jbpm 4 y sus particularidades.Mira, quiza me podes dar una mano.Tengo una situacion en la que tengo forks anidados, es decir lanzo un fork con tres tareas,imaginemos tarea 1 , tarea 2 y tarea 3,. la tarea 1 y 2 convergen en un join llamemoslo Join (1 .2) a modo de ejemplo. La tarea 3 aun no necesita ser cerrada.Continuando con la ejecucion finalizada la tarea 1 y 2 , se lanza una tarea intermedia,llamemosla (intermedia) q esta intermedia converge en un nuevo fork2 (tarea 4 , tarea 5) q se cierran en un Join, pero sobre el join este, tambien converge la tarea 1, la cual lance al ppio.Bueno, la cuestion es esta, el ultimo join respeta q se complete la tarea 1 y las tareas 4 y 5) como debe ser, pero el tema es q cuando lanza el fork 2.lanza las tareas 4 y 5 , pero me repite la tarea 4, nose porq.Internamente nose como funciona, y no lo he podido resolver.Si viste algo similar o se te ocurre algo. estare agradecido.Si queres te puedo adjuntar un png del proceso, asi se entiende mal, ya q soy bastante malo redactando :SSaludos.Cbaz.

Felipe - zFcWeU55uQ

It is good to see some clear thought and corcenn for the limits of the flow-centric emphasis of most BPM. As with procedural code, the more you try to model a real business, the more complex and tangled the flowchart becomes and, consequently, the more maintenance becomes a technical matter at which even the most skilled become less productive as the logic grows. As this happens, it certainly drifts from a business model to an implementation. We believe the cure involves both an emphasis on decisions (not just from the BRMS side, as advocated by James Taylor, but also from the BPM perspective) and a more knowledge-centric approach. This knowledge centric approach should include decisions, obviously, but also the vocabulary (e.g., SBVR) and ontology (i.e., the model). Until BPM and BRM share vocabularies and models, BPM mayappeal to the business but be largely confined to IT.Parenthetically, I believe that JBOSS, which has both the jBPM platform and JBOSS Rules / Drools, is positioned fairly well to lead the converging markets in this regard. http://qgstpgddvvk.com [url=http://yldxceups.com]yldxceups[/url] [link=http://pqzqjw.com]pqzqjw[/link]

Open - DIGbX2xK99z

the business<a href="http://ovnylpaxxoc.com"> pserocs</a> context is supported just for jBoss jBPM or other BPM can be used as well?At the moment only jBPM is supported, but if you have a specific BPM you would like supported, feel free to ! We're always looking to add support for new integration points.contexts are replicated across a distributed environment? Meaning a conversation started on a server in a cluster will be having the same context if a next request goes to a different server?Yes, Seam was developed from the ground up to support clustering. Conversation state is maintained in the HTTPSession so data replication will need to be enabled. If you are using EJBs, stateful session bean replication may also need to be enabled. Simply refer to the documentation of your AS to find out the details.

Mayumi - AhwpKagbJ2Qp