The trend in BPM among big vendors is to leverge a BPM engine (such as a BPEL one) and a rules engine together as a foundation for everything in their middleware suite--much of which does not entail human interaction. I just returned from a meeting with Oracle (read sales pitch) in San Francisco last week at which this was precisely their message.
In such an environment processes will be worked on by analysts and back-end developers, while front ends will be built by other individuals. You wouldn't want a core process def deployed every time a GUI developer wants to move something around. There is a genuine need to keep presentation specific data out of the core process def in the work flow world just as you would want to keep your presentation logic separate from business logic in any other multi-tiered application. Anything else would be limiting your solution to very specific use cases, and any solution that makes a policy of muddying the separation of concerns will not scale across the enterprise, regardless of whether the solution is an open standard or not. -Britt View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3912686#3912686 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3912686 ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
