Hi Tony,
I think the point you raised has been pretty much exhaustively elaborated by the
previous posters. What I want to add is that as somebody who has to switch
between SpringMVC and Stripes on a periodic basis - my experience is that
Stripes wins hands down.
Our company started a couple
Soren Pedersen wrote:
I have not tried Spring MVC. I dropped it when I looked at the XML
configuration file(s)...
Perhaps this has gotten better lately, I don't know.
SpringMVC has really improved in this area. Since version 2.5 (current
version is 3.0.X) you can basically do
Nikolaos Giannopoulos wrote:
Encapsulation in OO IMHO pertains to the class as a whole not the method
level. If you want to encapsulate at the method level then your going
to have a hard time not allowing someone to access and affect other
attributes of the class (e.g. other
Hi Tony
I agree IF Stripes would allow you to supply parameters for Action Methods,
like Spring MVC or JERSEY (REST), that would mean a good cleanup and better
encapsulation.
/Jeppe
It is difficult to get a man to understand something when his salary depends
upon him not understanding it.” -
Hi folks,
This has already been discussed on the mailing list (not so long ago).
The debate is open, and ultimately it's a personal preference : some prefer
method parameters a la Spring, others favor properties.
I think there is no answer here : both methods have their pros and cons, and
will
Again, I'm not attempting to prove that SpringMVC is better than Stripes,
the question of interest is whether Stripes encourages bad practice from an
OO point-of-view?
I suppose it depends on your definition of OO - I use subclassing in my
ActionBeans so that I can share common parameters and
of just the id?
That's even more trivial to do if your user converter takes the id.
Christian
-Message d'origine-
De : Tony Drago [mailto:do...@mailinator.com]
Envoyé : March-03-11 4:52 AM
À : stripes-users@lists.sourceforge.net
Objet : Re: [Stripes-users] re quest/response scoping
trivial to do if your user converter takes the id.
Christian
-Message d'origine-
De : Tony Drago [mailto:do...@mailinator.com]
Envoyé : March-03-11 4:52 AM
À : stripes-users@lists.sourceforge.net
Objet : Re: [Stripes-users] re quest/response scoping
Nikolaos Giannopoulos wrote
-Message d'origine-
De : Tony Drago [mailto:do...@mailinator.com]
Envoyé : March-03-11 4:52 AM
À : stripes-users@lists.sourceforge.net
Objet : Re: [Stripes-users] re quest/response scoping
Nikolaos Giannopoulos wrote:
Encapsulation in OO IMHO pertains to the class as a whole
On Mar 3, 2011, at 1:52 AM, Tony Drago wrote:
// ANNOTATIONS OMITTED FOR BREVITY
class MyController {
public String deleteUser(Integer userId) {
userService.deleteUser(userId);
return redirect:/listUsers;
}
public ModelAndView addUser(User user) {
Hi,
First of all, I promise I'm not trolling. I'm going to say some critical
things about Stripes here, but my intention is to understand whether I'm
missing something, not to offend. If you don't like to read criticism of
your favorite framework, you should probably not read any further. Now
Hi Tony
We can all learn from criticism, so in my opinion it is great to get your
view on this :-)
I have not tried Spring MVC. I dropped it when I looked at the XML
configuration file(s)...
Perhaps this has gotten better lately, I don't know.
Let me explain the way I see it.
Stripes has from
Tony,
Comments in-line...
Tony Drago wrote:
Hi,
First of all, I promise I'm not trolling. I'm going to say some critical
things about Stripes here, but my intention is to understand whether I'm
missing something, not to offend. If you don't like to read criticism of
your favorite
13 matches
Mail list logo
