On Tue, 23 Oct 2001, Guy Rouillier wrote: > I think the list of tasks and their order should be done external to both > the messages themselves and to the individual tasks, i.e., in a config file > somewhere/somehow. That way tasks can be added, removed or reordered > without changing anything other than the config file. Makes the individual > tasks and messages more autonomous and therefore easier to write, and also > makes the workflow easier to manage.
so something like the struts workflow (http://jakarta.apache.org/struts/proposal-workflow.html)? yeah, that makes sense. what about if you wanted the message to go from one server to another? for instance, have JBoss instances A & B, A has X and Y on it and B has Z. Now a message is sent to instance A, which then (from the config file) creates the list of tasks and sends the message off for the first task - X@A. So instance A gets the message, does task A, finds the next task is Y@B and sends it to B... etc.. I know this isn't quite what you said (I assume what you mean is that the dispatcher will read the list of tasks and then execute each one in a loop fashion), but the (currently hypothetical) requirement I have been given (yes, hypothetical && given) is that the system needs to be able to be distributed. thoughts? cheers dim _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
