On Tue, 23 Oct 2001, David Jencks wrote: > How is this better than simply having each task output its processed > messages to a specific queue, and routing by hooking the receiving mdb's > upd to the appropriate queue? I'm assuming that it is or could be easy to > manage the queue subscriptions. Then you don't need the dynamic workflow > manager at all. Am I missing something?
so say one task is a "retrieve user info" task. This task needs to be executed before a number of other tasks, "login", "send password", etc... So I should send a message to the retrieve user info task, which then populates the message with the user info, and sends it to its output queue. I should then configure the login and send password MDBs to both listen to that queue (topic would be required here wouldn't it?). I'm not sure how you propose which subsequent task is executed. Is it the case that there is something int he message, and some filtering done at the next MDB, or is there something else I'm missing? cheers dim _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
