I have a general sense of agreement with what you wrote, since I've worked with process editors at m-Qube and we've taken a similar approach. See http://m-qube.com/html/prodServ/studio.html
One interesting thing is the editor tool is a Java applet and the process logic is stored on the server. Having the tool done as an applet means the business users always can access tools. Hosting the code on the server also means the user has the latest version of the tool. Also, as a business tool, controlled content management of the "flow" is important. There are ways to schedule deployment and test new process flows with the tool. This can only really done by using a centralized server. As an aside, I see a bit of long-term synergy with rules engines and process management. I wonder if you can explain what is being done to integrate Drools and jBPM at the tool level? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3962356#3962356 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3962356 _______________________________________________ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
