[jboss-dev-forums] [Design of JBoss jBPM] - Re: including graphical information in the process definitio

[camunda]

It's difficult to decide that issue I think.

On the one hand, I would be glad to have it one file. We do some XSLT-Transformation on the processes, for example to generate a processs documentation website, using a imagemap on the process. There it is very unhandy to have 2 different files and it would be cool to have only one file.

Also I think is easier to keep everything in sync, if we have it in one file (for example renaming a node without using Eclipse-Plugin: You must also change the node name in the gpd.xml).

But on the other hand, I like the very straightforward process definitions, because I often work directly in the XML. Too much informations about diagram would be really discuting there. I like the example from Koen, with all the bendpoints inside the diagram. That is not nice for modelling the process.


So maybe I will vote for 1 file, with the most important informations (x,y of a node) in the section of the process definition and more "unimportant" additional stuff (like bending points of a transition) in a second section.


One additional question from me: Whats then your oppinion, where to put other additional stuff (user gui form mapping, maybe some additional business variables like cost per task, ...)? Also inside that XML? Or make a own section for everything?

By the way: How is that problem solved in other engines?

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4043458#4043458

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4043458