Re: JSF 2.0 a lot better was ->Re: Why use PHP? What are the disadvantages?

Here are some of the ones we've found so far:

- Facelets replace JSPs as the primary view language.

- Some components can be defined using facelets
entirely, instead of having to write Java code for
customization.

- Ajax is baked in well enough to do some fairly
sophisticated things (partial rendering) without
JavaScript.

- XML configuration is no longer required.

- Beans can have custom scopes that don't require
as much (if any) housekeeping code.


-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx] On Behalf Of Aaron Bartell
Sent: Wednesday, April 21, 2010 1:22 PM
To: Web Enabling the AS400 / iSeries
Subject: [WEB400] JSF 2.0 a lot better was ->Re: Why use PHP? What are the disadvantages?

Could you expound? I used the initial JSF release and liked some parts a
lot and others were productivity drainers.

Aaron Bartell
http://mowyourlawn.com
http://mowyourlawn.com/blog/


On Wed, Apr 21, 2010 at 12:13 PM, Thorbjoern Ravn Andersen
<ravn@xxxxxxxxxx>wrote:

Den 21/04/10 00.02, BButterworth@xxxxxxxxxxxxxx skrev:

I am not familiar with JSF, but would like to learn more about the Spring
and Grails Frameworks in terms of Java-type web development. I've read a
lot of negative criticism over JSF, but maybe 2.0 will be better. I am

JSF 2.0 is a _lot_ better!

(and in JEE 6)

--
Thorbjørn Ravn Andersen "...plus... Tubular Bells!"