having looked at the javadocs and documentation and stopping short reading the spring codebase in detail, a question I'm having is looking for an appropriate design method of controller chaining.
The context of the question is using a FormController in conjunction with commons validation, and then wanting to pass the request off to a more centralized application-specific controller for handing business-tier requests before moving forward to the view layer. It matters as the http form could exist on any html page of the webapp.
I've not seen direct support for chaining controllers. I could call the extended Controller directly from the FormController, however that requires a try-catch and then I'm not sure if passing the exception up is the best solution. I can also have the FormController's SuccessView() forward to a bean mapping handled by the second controller.
Architecturally, is there a desired way of implementing more than one controller for a specific request?
thanks in advance,