Hi Jamie, Thanks for the information - we'll give BpmScript a closer look, then. About the email correlation, I guess we'll have to come up with a way of including some kind of session identifier when a message leaves the bus - and extract it once the reply arrives.
I'll come back once we have more questions or feature requests. Ciao, Philipp > -----Mensaje original----- > De: Jamie McCrindle [mailto:[EMAIL PROTECTED] > Enviado el: lunes, 09 de octubre de 2006 23:39 > Para: [email protected] > Asunto: Re: Best practice for implementing message flows/chains with human > intervention > Importancia: Baja > > Hi Philipp, > > It sounds like you need some Business Process Management (long running > stateful processes with human intervention). > > All of your nominees should be up to the task, some requiring more > work than others. I can only speak for BpmScript which is related to > Apache Flowscript in that they both use JavaScript continuations. It > currently has a relatively simple worklist service but tasks are > completed using the web console. Processes will pause / persist > themselves while waiting for new responses (e.g. human interaction). > You can use the web console to view / manage running processes and > process instances (http://www.bpmscript.org). > > BpmScript Beta-2 is close and should include: > > - Database backed persistence for processes and tasks > - Basic correlation service > - Some bug fixes > - Upgrade to Maven 2 > > While email correlation is in the pipeline, you'd have to write your > own for now (probably true for most of your nominees?). > > That said while a 1.0 release hopefully isn't too far away, it's > release date is currently "when it's done". > > If you do try out BpmScript and would like to see some features or > would like some help, give me a shout. > > cheers, > j. > > On 10/9/06, Rossmanith, Philipp <[EMAIL PROTECTED]> wrote: > > Hello, > > > > In our scenario, we have a number of endpoints that we need to > > combine/aggregate into larger flows/chains. At points, some of these > > flows/sessions require human input - hence, no assumptions can be made > > about how long the corresponding step may take. A typical example would > > be that an endpoint sends a mail to a user asking for confirmation. > > > > Let's call the execution of such a flow/chain a session. The session > > would have to execute until the point in which the timeout occurs. It > > would then have to perform the request causing the time-out and persist > > itself. Once the answer to the time-out request arrives (marked with an > > identifier for the session), it would have to pick up the execution at > > the point where it had stopped. > > > > This is something that for instance Apache Cocoon provides with its > > Flowscript. > > > > Which of the available ServiceMix components would be best suited for > > such a purpose or could be used/enhanced for implementing one? > > > > From the ServiceMix documentation and the discussion I found here > > (http://www.nabble.com/-Heads-up--ServiceMix-BeanFlow-library-available- > > tf1614778.html), I reckon that the nominees would be: > > - Beanflow > > - BpmScript > > - bpe and eip components > > - Rules and script-based routing > > > > Thanks in advance, > > Philipp Rossmanith > > > > This e-mail may contain confidential or privileged information. Any > unauthorised > > copying, use or distribution of this information is strictly prohibited. > > > > Este mensaje electrónico puede contener información confidencial o > privilegiada, por lo > > que está completamente prohibida la copia, el uso o la distribución no > autorizada de > > dicha información > > > > Aquest missatge electrònic pot contenir informació confidencial o > privilegiada i està > > completament prohibida qualsevol còpia, ús o distribució no autoritzada > d'aquesta > > informació. > > > > Mezu honek, enpresaren jabetzapeko edo legalki babestutako isilpeko > informazioa izan dezake. > > Zu ez baldin bazara hartzailea, mesedez bidaltzaileari jakinarazi > iezaiozu eta mezua ezabatu, > > ez ezazu gorde ezta birbidali ere, baimendu gabeko bere erabilera > debekatzen da eta. > > > > This e-mail may contain confidential or privileged information. Any unauthorised copying, use or distribution of this information is strictly prohibited. Este mensaje electrónico puede contener información confidencial o privilegiada, por lo que está completamente prohibida la copia, el uso o la distribución no autorizada de dicha información Aquest missatge electrònic pot contenir informació confidencial o privilegiada i està completament prohibida qualsevol còpia, ús o distribució no autoritzada d'aquesta informació. Mezu honek, enpresaren jabetzapeko edo legalki babestutako isilpeko informazioa izan dezake. Zu ez baldin bazara hartzailea, mesedez bidaltzaileari jakinarazi iezaiozu eta mezua ezabatu, ez ezazu gorde ezta birbidali ere, baimendu gabeko bere erabilera debekatzen da eta.
