This seems to be a lively discussion, so I thought I'd throw my hat in....
In regards to the original post, this is more or less exactly what we were trying to do at our organization also -- a simple interface for the engine that would allow client apps to instantiate workflows. Here is the result: http://code.google.com/p/fluxr/ Fluxr wraps OpenWFEru in a stand-alone web server that provides a REST interface for client apps. So for example, to instantiate a workflow, you would use a REST client (like ActiveResource) to place an HTTP POST call to: http://your.fluxr.server/workflows?workflow_definition=my_approval_process.xml Or if you want to get info about all running workflow processes, do a GET call to: http://your.fluxr.server/workflows Now, fluxr is still a bit of a work-in-progress... a stalled one at that, because the company where I was developing this for decided to go with a different BPM solution (lack of a GUI tool for building OpenWFE workflows definitions was the deal-breaker)... but it is more or less functional at this point. My next step will be to provide a proper UI for viewing the status of a workflow... right now the HTML output is very simplistic, and not really end-user ready. Hope this helps. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "OpenWFEru dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/openwferu-dev?hl=en -~----------~----~----~----~------~----~------~--~---
