There is a disadvantage to that approach, however, namely that it creates new WebContinuations when you redisplay the page (i.e. when sendPageAndWait is called again). The approach I suggested reuses the same WebContinuation. Reusing the same WebContinuation also ensures that the hierarchy of WebContinuations exactly matches the sequence of pages (regardless of whether the page redisplayed, as in for example Woody's validation loop), making back button handling easy.
Ah yeah, reuse of continuations is something I've got to investigate, namely in Woody as you rightly point out. I tried to analyze JXForm's flow stuff, but failed to, as I got lost between the different form phases and continuation reuse. Can you give some clue on how we should refactor the woody redisplay loop?
Sylvain
-- Sylvain Wallez Anyware Technologies http://www.apache.org/~sylvain http://www.anyware-tech.com { XML, Java, Cocoon, OpenSource }*{ Training, Consulting, Projects } Orixo, the opensource XML business alliance - http://www.orixo.com
