[Springframework-developer] Spring Web Flow

[Will B. <Wil...@ra...>]

All,
=20
We have been using the Ervacon version of Spring Web Flow since version
0.7, and we are now attempting to migrate to the new code in the Spring
sandbox. In the process, however, I noticed that the decoupling of
actions from the request/response has made them more difficult to test.
Creating a RequestContext requires an Event and a FlowExecutionStack
which requires... Anyway, I realize that we could create a Mock of the
RequestContext, but this also requires that child elements like Scope
need to be mocked out as well. What is the motivation behind the
additional layers of abstraction and why are they necessary? Does anyone
best practices and/or examples for unit testing actions in the new
design?
=20
Thanks,
=20
Will Butler