"andyredhead" wrote : At the moment, the process definition xml contains infomation about the process. | | The more different kinds of things you put into that file, the harder it becomes to understand that file and the more likely you are to put people off from ever using jBPM. I disagree. People who don't want the added features, won't use them. And I think the general expectation is that people will use the GPD for building jpdl processes, so they probably won't see the XML at all anyway. Designing an XML document to be human-readable is, at best, an exercise in futility. However, I agree that adding information pertaining to one specific GUI implementation type is probably not appropriate. Perhaps a better approach is to have an attribute that holds a generic XML block as presentation information, and leave it up to the GUI implementation to interpret the block. For the forms designer, this block could be facelets-style xhtml, or some other XML schema with xhtml inside of it. As long as the XML namespaces are properly provided, pretty much anything is possible. Or maybe that's getting too complicated and we should just have a separate file. And again, if you don't want the GUI information, just don't provide it, and you won't have to look at it. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3979653#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...