Has anyone defined swimlanes externally to the process definition? (Does that even make sense?) I have many workflows that involve the same swimlanes, and right now I am cutting and pasting the XML into each process, which is not the idea situation for many reasons, the most obvious of which is that if I need to make a change I have to go through every file to do it.
But, I am not sure what the appropriate "other way" would be. Swimlanes do need to be associated with a specific version of a process definition, but maybe instead of defining the swimlanes in the process definition xml just the reference to a swimlanes definition file (new concept) could be in the process definition xml and the jbpm engine could process it when it loads the process definition from the XML (into memory or into the DB). Any thoughts on the pros/cons of this or other methods to achieve this end? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4005655#4005655 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4005655 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
