make AbstractMVCView less dependent on the servlet view object to form a good abstract base, make binding a strategy design pattern

I put together a swing based integration point with webflow. A couple of things came up that would be helpful:

a) Make AbstractMVCView just an AbstractView with the view object untyped. A specific subclass can then provide typed access to the object. You can also do this with AbstractMVCFactory. In light of not using generics in the release (until 1.5 is supported) this would help reuse the factory and view objects in non-web settings.

b) Make the binding and validation on request parameters inside the AbstractMVCView object a strategy design pattern that is pluggable. This probably means that a configuration object has to be available on the ViewFactoryCreator to plug in the binding strategy object.