Acrophobia and the Controllers' Hierarchy Tree

[carrijo]

Hi,

I would like not to be ruminating over this same idea, but
what's simple (SimpleFormController, got the quibble?) for
some, ain't that much for others! :)

My question:

What controller am I supposed to use in a flow which is not
trivial enough for SimpleFormController and whose execution
graph forks in such a way that AbstractWizardFormController
becomes a bit awkward to handle the situation?

Just in case you get interested: I've had problems keeping a
reference to the command while using the SimpleFormController
in large flows. It simply vanishes whenever the flow reaches
a page with no <spring:bind>. And I really dislike the idea
of using hidden inputs just to keep the form object!

With so many misunderstandings about the inner workings of
those controllers, I would be glad having not to implement
subclasses of anything standing higher in the hierarchy tree
than the SimpleForm.

Its a kind of acrophobia!
But I'll keep trying!
Thanks!

[Colin Yates]

I would suggest looking at Spring Web Flow. Sounds like the right tool.