Spring just required simple pojo and their controller known as
ModelViewController have a formBackingObject.
But in struts1 we need to provide class that extends ActionForm class.
On 12/1/09, Gérald Quintana wrote:
>
> I think in Struts1 and Spring MVC, you have the Controller (call it
> ActionB
I think in Struts1 and Spring MVC, you have the Controller (call it
ActionBean or Controller) and the Model (call it FormBean or Model)
are separated. On the contrary, in Struts2 and Stripes both of them
have merged.
Given that Business Service or Data Access Services are usually
injected in Contr
I am got experience using Stripes, Struts and Spring, and I prefer Stripes
over those framework because Stripes is easy and required only web.xml
instead of Spring (a lots of xml) and same goes with Struts. However, using
Stripersist that have integration with Spring (AOP and DI framework) is
prett
Great; thanks for taking the time to read it.
Mike McNally wrote:
> That looks OK to me (though the thing about separate methods for GET
> and POST is not really true for my application anywhere).
>
> The coolness of Stripes parameter-property mapping is (for me) easier
> to appreciate on the in
That looks OK to me (though the thing about separate methods for GET
and POST is not really true for my application anywhere).
The coolness of Stripes parameter-property mapping is (for me) easier
to appreciate on the input side, especially when there's something
akin to Stripersist to handle impl
Thinking out loud; did I make any mistakes about how Stripes works?
http://lumpynose.wordpress.com/2009/11/29/action-based-frameworks-vs-spring-mvc-under-the-hood/
--
Let Crystal Reports handle the reporting - Free Crysta
