On 27.11.2007, at 21:04, Jeroen Reijn wrote:
Torsten Curdt wrote:
If I can write and debug javaflow in Eclipse then that seems to be a
superior solution, but the fact that continuations require 'add-
ons' to java
objects to make them useable maybe causes some side-effects that
can be
'gotchas'.
I am not sure how many people use javaflow in production. Surely
javascript has been tested quite extensively. The javaflow
implementation is still not officially released and has some
little gotchas ...but indeed debugging your flows within Eclipse
is a nice thing. But I am biased anyway ;)
We (at Hippo) are using flowscript in production a lot and it has
always worked very well. I know there are some people that use java
flow in production as well, but I have no personal experience with
it.
About debugging Java flow in Eclipse. That actually does not look
like a real big problem, unless i'm missing something. I've been
debugging numerous Cocoon applications with Eclipse.
Well, the instrumention of javaflow does make it a little more
special than just debugging Cocoon ...but as demo'ed at the GT in
2005 - it does work! :)
cheers
--
Torsten
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
