about processes and engines

in reply to Greg (ja vs ru)

Greg posted this comment, expressing his concerns about OpenWFEja versus OpenWFEru.

It’s true that OpenWFEru potentially endangers the classical Java OpenWFE. Division of the effort, loss in the focus.

> OpenWFE is (no offence, it is certainly very powerful and stable as-is, but is also constantly moving and improving)

Well, these days, it slowed down a lot. And it still lacks snappier interfaces.

> being attracted by the new and shiny that ruby is.. and leave the Java project as an orphan

I don’t plan on leaving OpenWFE an orphan.

I don’t feel Ruby is that new and shiny, it’s been out of the spot light for a long time (the night of the Orient is the day of the Occident… And vice versa). Yes, it’s shiny, but Rails is shinier.

Rewriting the core of OpenWFE in Ruby proves to be a great simplification work, because a) expressing self in Ruby is easier, b) everything is clear in my head.
OpenWFE Java could benefit a lot from the lessons learnt in porting OpenWFE to Ruby. That could be materialized in the medium term as an OpenWFE [Java] 2.0.

I lack static typing sometimes but unit tests do compensate a lot.

The Ruby community might also be more open than the Java community. More energy, more youth, more ideas. Has Java turned into some Cobol ?

> Also, I’m curious as to what your plans are regarding the keeping of compatibility and synch between the 2 versions.

OpenWFEru was born as “openwfe-ruby”, an access library from Ruby to OpenWFE (over REST), a simple wrapper implementation around an interface (a protocol). (What’s fun is that some other people use OpenWFE directly from the browser forms via this REST interface).
In that light, some of the more recent suite tests around OpenWFE Java are written in Ruby (the vast majority of the others are written in Ruby).

OpenWFEru is also able to receive workitems directly from the Java engine and vice versa. It makes for interesting distribution scenarii.

So OpenWFEru comes through an interface shared with the initial Java implementation and is evolving to respect another contract : the OpenWFE process definition language.

Orphanity threats could materialize in another way. Alain the other day said : “Well, basically, once the Ruby workflow suite is complete and runs fine on JRuby as well, you could dump the Java version” and he smiled.

(Don’t worry, I favour the OpenWFE 2.0 scenario)

Written by John Mettraux

December 1, 2006 at 9:15 am

Posted in openwfe, openwferu, ruby

4 Responses

Subscribe to comments with RSS.

  1. Ah well, if it would really work perfectly w/ jruby, why not, after all – but that’d seem just too far fetched, and would make my life harder when i’d have to debug ;)


    December 1, 2006 at 9:38 pm

  2. And hey, thanks for the post ;)


    December 1, 2006 at 9:43 pm

  3. the following link is not opening.. could you pl do the needful


    December 6, 2006 at 12:13 pm

  4. KingKong,

    follow that link :

    John Mettraux

    December 6, 2006 at 1:38 pm

Comments are closed.

%d bloggers like this: