Hi Geraint, 2007/5/14, GHZ <[EMAIL PROTECTED]>: > > Is there a web application to interact with the work items, is it > planned that this will be part of OpenWFEru?
It's not yet planned. > How does the OpenWFEru components compare to the components listed > here? > > http://www.openwfe.org/manual/ch02s05.html * Engine : it's here, 100%. * Worklist : currently only store participants are available (http://openwferu.rubyforge.org/participants.html#HashParticipant and http://openwferu.rubyforge.org/participants.html#YamlParticipant). I'm gathering a set of stores to build a real worklist with the same REST interface as found in OpenWFE [Java]. Work is under way, right now. * Webclient : you are asking for it, but it's not [yet] here. * Apre (Automatic Participant Runtime Environment) : the ease with which you can write a Ruby participant in OpenWFEru (for example : http://openwferu.rubyforge.org/participants.html#BlockParticipant) makes it almost unnecessary. But as some people are willing to have the engine in a different RVM than the apre, they could investigate DRB (http://whytheluckystiff.net/ruby/pickaxe/html/ospace.html#UG) or use some of the workitem dispatchers available in OpenWFEru (http://openwferu.rubyforge.org/participants.html#SocketParticipant or http://openwferu.rubyforge.org/participants.html#SqsParticipant or ...) to distribute their application. * Droflo : there is a prototype of it based on Rails available (http://groups.google.com/group/openwferu-users/browse_frm/thread/4f2d387c83e03ee1). I have a friend working on another designer (based on Adobe's Flex), but he's been rather busy these days. I'd like to have such a tool soon, I sincerely think that a graphical view of a process (in a browser) is a good thing and this is easy to generate from an OpenWFE process definition. > I'm wanting to investigate this workflow tool on top of web services > that we already have defined in an existing project. Could I play the devil's advocate and ask why you wouldn't use a BPEL-based engine ? > Long term I'd want to dynamical generate a wizard type web UI based > upon the the workflow and the attributes that are required for each > workitem (would need some client side logic to 'wait' for synchronous > background workitems). > In the short term it would be useful to have an existing web interface > I can use to complete work items, hence my question about the web > client for openWFEru > > An example of what I'm talking about would be: new customer sign-up > with optional product purchase: > 1) Get Customer details (name, email) > 2) Register Customer > 3) If Registration OK then get product info (product, quantity) > > Assuming the automatic work item for registering the customer (web > service call) can be considered synchronous. The user experience > should be two forms with the fields specified in the workitem, the > product screen being displayed automatically after the customer sceen. > > Does anyone have any experience in using openWFE(ru) for this type of > model? There are people that implemented such processes on top of OpenWFE. For OpenWFEru, you might want to take a look at Pat Cappelaere's work : http://www.geobliki.com/ and http://www.slideshare.net/cappelaere/improving-operational-space-responsiveness > My tenancy would be to develop the web-app in Python rather than > switch to yet another web framework, although I would consider > switching to rails if there was work I could leverage. I haven't been giving a high priority to an OpenWFEru webclient because Rails is here and makes it easy for people to develop custom (forms). And also, my experience is that when you develop a generic webclient, people immediately think that it's the only client and they simply have to customize it. It's OK for simple cases but it might not scale for any bell or whistle. Maybe someone will step in and develop that OpenWFEru webclient on top of rails, it's open source after all. Pat has taken another approach and is using xforms (http://skimstone.x-port.net/what-is-xforms / http://www.formfaces.com/) to build, well, forms. About Python, there is an ongoing effort for porting OpenWFEru to Python : http://jmettraux.wordpress.com/2007/04/27/from-ruby-to-python/ and the REST interface I'm retrofitting from OpenWFEja to OpenWFEru would allow you to 'pilot' and OpenWFEru engine + worklist from Python (via http://www.openwfe.org/openwfe-python.html), but as already said in this email, it's an ongoing effort. I hope I have answered your questions, best regards, -- John Mettraux -///- http://jmettraux.openwfe.org --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "OpenWFEru users" 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-users?hl=en -~----------~----~----~----~------~----~------~--~---
