[jboss-dev-forums] [Design of JBoss jBPM] - Re: extending form / task functionality

"david.lloyd(a)jboss.com" wrote : | 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. | At the moment I use the visual diagram part of the GPD to draw the flows and then either the xml source view in the GPD or the eclipse xml editor direct to add actions to events in jBPM. Some events have multiple actions and the order in which the actions are fired can be important... So I have to deal with the xml direct - or is there a better way? ;) Another way of putting my point forward is to say that jBPM cannot solve all problems for all applications, so instead it should do its bit well. If there are problems with the way some other part of an application calls it, it should be the responsibility of the other part of the application to deal with it - not jBPM. Would it not be better to move core parts of jBPM forward (such as the use of JMS for asynch processing or maybe using the ejb timer service for scheduled things within a process) rather than "fiddling around" with non-core things? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3979660#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...