There are also different aspects to consider,
other than technical advantages. For instance, I work in a
large
corporation which has oodles of java developers and
many web app projects going on at once.
Our decision (a commitment made over a year ago....) to
use JSF, and not struts, was based on the fact that
JSF was being introduced into J2EE. If you consider the
fact that in a large corporation developers come and go every
week
you must choose technologies that are prevalent in the
community...this way you can optimize your chances that new
developers coming
in every week will be familiar with the technologies and can become productive
in a shorter time span.
(Gees - I sound like a projecty manager!).
Furthermore, emphasizing this idea somewhat further, we have tried to
avoid
coding our own components, in order to have less code
for incoming developers to absorb....and BTW, we have
developped
a pretty complex web app using ONLY the base components
provided by the myfaces impl.
So to recap: from a development point of view in a
large corporation, we found we really had little choice but to
use
JSF, because it is safer, in this context, to remain in keeping with J2EE
tendancies in the long term.
If you are developing for a smaller company, our
reasoning might not apply :)
HTH,
Mark
great explication !!
De : Fadil [mailto:[EMAIL PROTECTED]
Envoyé : mercredi 20 juillet 2005 10:29
À : MyFaces Discussion
Objet : Re: Justification to switch to JSF from Struts?
On 7/20/05, CONNER, BRENDAN (SBCSI) <[EMAIL PROTECTED]> wrote:Some of advantages that our team recognized when we decided to convert
to JSF:
1. Automatic type conversion of bean elements (i.e., don't have to
translate everything to and from String)
2. Bi-directional conversion between browser info and bean info ( i.e.,
both encoding and decoding capabilities built in, rather than just
decoding capabilities)
3. Validation and conversion is more robust, extensible, re-usable, and
concise
4. We can now define and re-use (not just copy and paste) actual
components now, both in-house and third party, thus drastically reducing
coding the same things over and over.
5. Just as Struts codified best practices that people were hand coding
already, JSF is also codifying the next level of best practices that
people have had to code by hand when using Struts (e.g., the JSF
lifecycle events).
6. Virtually eliminates any kind of logic needed in the JSPs, increasing
reliability of code.
7. Virtually eliminates any need for the application logic to directly
access the Session and Request attributes/parameters, increasing the
reliability of the code.
The bottom line implications of the above were:
1. Less coding in both the Java code and the JSPs
2. More opportunities for re-use (both in-house and third party)
3. Because of 1 and 2:
a. Faster development
b. More reliable applications
- Brendan
-----Original Message-----
From: Lindholm, Greg [mailto:[EMAIL PROTECTED] ]
Sent: Wednesday, July 20, 2005 8:50 AM
To: [email protected]
Subject: Justification to switch to JSF from Struts?
I've been using Struts for a while and have just started learning JSF.
I'm reading "Java Server Faces In Action" right now and have "Core Java
Server Faces" sitting on my desk.
I'm liking what I'm seeing and seriously considering using JSF/MyFaces
for my next project. However, I need to be able to justify a technology
change to my manager (and to myself). There is a non-trivial cost
whenever you switch to a new technology. (Learning, testing, developing
methodolgies, training others, etc.)
I'm looking for reasons to justify a switch to JSF from Struts.
I started to prepare a list of "short-coming" with Struts from my own
experience.
The JSF designers must already have this list. Where can I find it?
I guessing this is a popular topic but I've search and not been able to
find a consise list yet.
TIA
Greg
