Hi
SpringMVC has seen some radical changes lately, but they IMO still
have one major drawback - their databinding.
Let's say that you in Stripes bing to "person.personName.firstName".
Lets say that you've fetched a person entity from the database, but
the person's getPersonName() property accessor returns null.
SpringMVC will fail to insert the firstName value because personName
is null. Stripes handles that elegantly by creating a PersonName for
you. So with Spring you ALWAYS have to make sure that you don't have
any intermediate properties in a binding that are null. This is not a
concern with Stripes.
Performance wise I would assume that Stripes is a little bit slower
than Spring MVC (haven't measured this though), in that Stripes
created an ActionBean for each request (SpringMVC can do the same, but
seems to prefer singletons), Converters' are per call, etc. But then
again, the JVM is optimized for shortlived object creation, so
eventhough Stripes _may_ be slower, it shouldn't be noticeable.
Also if you use a storage backend, such as a database through either
JDBC, Hibernate, JPA, without any transparent clustering (like
Terracotta), you are for sure going to see that the backend is the
limiting factor, performance wise, and not Stripes.
Regarding scaling in terms of development speed, I would say that
Stripes is a clear winner. We've created a very big web application
with more than 150 ActionBeans, and out of the box Stripes delivered
90% of the functionality that we needed. The remaining , which we
related to using an exposed domain model based on hibernate, was
elegantly created without having to change core Stripes code or patch
Stripes. We did it all by creating custom converter/formatter and
interceptors.
/Jeppe
On 07/10/2008, at 18.47, ping lu wrote:
Hi, Strips community,
Currently we are evaluating web framework for a very big enterprise
project. Stripes seems to be the pick at this moment.
Though we still need more materials to support the decision (for
politically correctness). Maybe your knowledge can easily help us
out with some information:
1. Could you please list any relatively large scale enterprise
applications used by Stripes?
2. what is the biggest advantage (or weakness) Stripes over Spring
MVC (2.5 or plus) in particular? (since Spring MVC has already been
used in our organization).
We especially concern about "request/response performance" and
"scalability".
With those information, we may able to make our final decisions. Any
help from you is greatly appreciated.
regards,
H. Lu
Stay up to date on your PC, the Web, and your mobile phone with
Windows Live. See Now
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
Build the coolest Linux based applications with Moblin SDK & win
great prizes
Grand prize is a trip for two to an Open Source event anywhere in
the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/_______________________________________________
Stripes-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/stripes-users
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Stripes-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/stripes-users
