Here is my response to such questions :

1.  Why do you prefer Struts over any other web application framework?
(Tapestry, JSF, Maverick, WebWork, etc)

I don't use Struts because I think it is the best framework. I use it because 
my dev team has some experience using it. Having to change MVC framework may 
reduce productivity. To make me change to another one, it may be really 
intuitive and easy to learn. I haven't took a look at SringMVC or any other. 
Perhaps I'm missing something...

I also use struts because my customer have read this word on the net and agree 
using it. It's a stupid argument, but it is the stronger I can give to my boss.


2. Why should _I_ prefer <insert framework here>?

I realy think lot's of MVC framework may be usefull. I think they can also be usefull to help Struts becoming more flexible / easy / fonctionnal. For example, SWF introduces use of XMLHttpRequest for a more dynamic web GUI. Maybee some future Struts extension will do the same... This function can be usefull for some projects and useless for others, so I can't say if SWF is *better* than Struts.

In short, consider your developpers exeprience (framework learn cost) and the functions that may be usefull to you to decide what framework to use.

Nico.


Justin Morgan a écrit :

Thanks...

I recently picked up Rod Johnson's J2EE Design and Development (ISBN:
0-7645-4385-7), and Chapter 12 is titled "Web-Tier MVC Design"...  I'm
going to assume this chapter is pretty similar to the one you mention.

I agree with you that this author is incredibly clear-minded, and I'm
soaking it all in.  Most of the book is model-neutral, and focuses more
on good practices and patterns, which is great because we have not
decided on a model yet.  But in chapter 12 he only really discusses
Struts, Maverick, and WebWork.  I was hoping for some commentary on JSF
and Tapestry as well, especially regarding why one might choose one over
the other.

It all boils down to two questions:
1.  Why do you prefer Struts over any other web application framework?
(Tapestry, JSF, Maverick, WebWork, etc)
2.  Why should _I_ prefer <insert framework here>?

The second question is not meant to make anyone defensive; I'm just
trying to get past


Thanks,

-Justin



-----Original Message-----
From: Dakota Jack [mailto:[EMAIL PROTECTED] Sent: Monday, March 07, 2005 3:30 PM
To: Struts Users Mailing List
Subject: Re: MVC Frameworks


Rod Johnson (author of Spring and one of the clearest thinkers I have
ever read IMHO) has a good discussion of the options in J2EE
Development without EJB in Chapter 13: Web Tier Design.

Jack


On Mon, 7 Mar 2005 14:19:47 -0600, Justin Morgan <[EMAIL PROTECTED]>
wrote:


Hi there,

I am currently researching different web application frameworks...


JSF,


Struts, and Tapestry specifically. We are planning to migrate a large
existing web application to a rigorous model 2 standard using one or
more of these frameworks, and I am looking for more information on the
differences between them. My research thus far has turned up only a


few


sources, and many of them seem religiously biased toward one of them.

If any of you have opinions, or better yet, articles contrasting these
technologies, please let me know.

Thanks,

-Justin

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]









This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to