User development, A new message was posted in the thread "Upgrade from JBPM3 to JBPM4 woes": http://community.jboss.org/message/523768#523768 Author : nick bauman Profile : http://community.jboss.org/people/nick.bauman Message: -------------------------------------------------------------- Hello, I'm looking into upgrading our process definitions and integration / embedding code written in JBPM3 to JBPM4. Our code does not use any application server like JBoss so we do not rely on container or third party integration. We also are not using any persistent store because we have our own cluster synchronization technology. Needless to say I see quite a lot has changed now that version 4 has arrived. The JBPM3 technology was more of a classic Finite State Machine. JBPM4 seems to have a new layer of abstraction: I see no sign of any GraphElement, Node, State, Transition, ActionHandler, ExecutionContext etc etc. I'm having a hard time seeing where these things morphed into or whether the original FSM idiom is simply gone. Stuff like "Swimlane" and "Task" strikes me as quite the departure so I'm not holding much hope. Currently we have several dozen process definitions ranging from 10 to 40 elements, the larger ones end up being around 1500 lines of XML. Is it even worth it to try and figure out where JBPM4 can fit into a migration strategy from JBPM3? I see some stuff that's named similarly in a package called org.jbpm...internal (that "internal" seems quite the red flag) that unfortunately isn't even close to the old code interface-wise. Specifically can anyone tell me where GraphElement, Node, State, Transition, ActionHandler, ExecutionContext may have gone or how they've changed? Thanks, Nick -------------------------------------------------------------- To reply to this message visit the message page: http://community.jboss.org/message/523768#523768