actually performing the heavy lifting of your business logic, but "glue"ing it all together. You can do any transactional handling in a
real java class which is then called by a simple flow. Does that meet
your need?
Geoff
Stephan Michels wrote:
Hoping I'm not too late. Please interpret this not as personal attack...
or something else. I like the idea of the flow, but the javascript
implementation inhibit me to take a deeper look into it.
+------------------------------------------------------------------+ | JavaScript Interpreter | +------------------------------------------------------------------+
[H] Our first and currently only[5] interpreter implementation is a Javascript implementation based on Mozilla Rhino which has been extended to support continuations.[6]
It just one solution. I don't like javascript, and the impression that all can be handle harmless in one Javascript function is dangerous, see handling transaction(hilbernate).
I would love to see an alternative implementation.
In my POV the flow belongs to the core, but not the javascript implementation.
