about processes and engines

XForms and OpenWFE

I had not noticed this fine piece of documentation at, though I knew about this team’s work.

So, this is about OpenWFEja and its old REST[less] interface.

What next ? Well, I ported this old interface to OpenWFEru so basically this XForms application should work out of the box with this open source Ruby workflow / BPM engine. But it’d be better to have a true REST interface to it, and this time, I wouldn’t implement any access library to it (the FormsPlayer guys didn’t need any).

It’s a bit vaporous, for now.

Written by John Mettraux

October 22, 2007 at 1:59 pm

Posted in openwferu, rest, workflow, xforms

5 Responses

Subscribe to comments with RSS.

  1. yes, vaporous and nebulous, misty and vague…but still interesting.


    October 23, 2007 at 12:42 pm

  2. Hi John,

    Funny you should spot that just at the time when I was looking at OpenWFE again!

    The context is that we’ve just switched our servers over to Amazon’s EC2, and that prompted us to think that we might set up some ‘images’ with some standard XForms applications on them. But when we went to search out the latest version of OpenWFE it wasn’t clear whether we should make the switch to Ruby or not.

    Are you phasing the Java version out? We have no preference either way (we use so many languages that one more won’t make a difference…), but if all development from here on in will be in the Ruby branch, then we might as well switch now.

    What do you think?


    Mark Birbeck, formsPlayer | +44 (0) 20 7689 9232 |

    standards. innovation.

    Mark Birbeck

    October 25, 2007 at 1:00 pm

  3. Hi Mark,

    I would recommend the OpenWFEru (the Ruby version), because it’s where the focus is now, and it’s way more open and easier (for me and you) to hack.
    All in all OpenWFEru is way better than OpenWFEja, and yes, all the development happens there.

    It features the REST[unful] interface that you know well, though it has been less tested than the Java original version.

    My goal is to provide a REST[ful] service quite similar to the Densha web application ( in scope (engine + worklist), it would be really different from the old REST interface, but not too much, maybe you have some flexibility and wait for it / help implement it / integrate it with FormsPlayer. The codename of this ‘webservice’ is ‘Kisha’ (steam train).

    Maybe you’d like to join the discussion :

    Best regards, glad to have news from you,


    John Mettraux

    October 25, 2007 at 3:51 pm

  4. Hi John,

    Thanks for that. I will join the lists once I have a few other things out of the way.

    By the way, we’re also doing some interesting stuff with EC2 and S3, and I’m hoping at some point to bring the whole package together! Have you looked at these?

    All the best,


    Mark Birbeck, formsPlayer | +44 (0) 20 7689 9232 |

    standards. innovation.

    Mark Birbeck

    November 13, 2007 at 9:42 am

  5. Hi Mark,

    I just looked at Amazon SQS because it’s so workflow-related, had no time to play with the others, I would be glad to help.

    Looking forward collaborating with you, have a nice day,


    John Mettraux

    November 13, 2007 at 10:05 am

Comments are closed.

%d bloggers like this: