My understanding is that the internal asynchronous messaging within jbpm is fairly limited, though it may be enough for my purposes.
For example, if I needed to run a bunch of ftp jobs at once, I might need a pool of "ftp runner" objects. These would sit around waiting for messages to ftp files. JMS would guarantee that a single request message was sent to one and only one object. My sense is that this is well beyond jbpm's internal messaging, but I'm not certain of the details. Can anyone comment on just how far you can go with jbpm internal messaging before you need JMS? Also, what is the state of JMS support in jbpm? I've seen several references to "to come". Thanks, Fred View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3936390#3936390 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3936390 ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
