I know what you mean. J2EE deployment descriptors are a perfect example of how bad things can get. However, UI-related data in a business process makes it less readable, as they are irrelevant to the business logic. Of course, if you assume that most of the time you'll be looking at the graphical view and regard the document as an interchange format, then merging all details in a single file makes complete sense. IMO this is a matter of the intention of the text representation.
I know jBPM 1.0 used a single file. What's the approach taken by other workflow products? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3912508#3912508 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3912508 ------------------------------------------------------- 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
