Win a copy of The Little Book of Impediments (e-book only) this week in the Agile and Other Processes forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

a thought about JSF and Java EE 5

 
ankur rathi
Ranch Hand
Posts: 3830
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
On one side, Java EE 5 "removed" all XMLs (DDs) and used annotation to save users to maintain a separate "information" file and swich editor. And on the other side, they are promoting JSF which requires huge XML file even for a small hello world application.

Somehow I think, JSF is certainly complex though I have no working experience of it.

What's say?
[ October 17, 2007: Message edited by: ankur rathi ]
 
David Sheth
Greenhorn
Posts: 17
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
That's exactly why many people are using Seam, as it does the same thing for JSF that JEE5 did for EJBs--eliminate the configuration files in favor of sensible defaults that may be overridden by annotations and/or xml.
 
Cameron Wallace McKenzie
author and cow tipper
Saloon Keeper
Posts: 4968
1
Hibernate Spring Tomcat Server
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
When you see how Hibernate and JPA eliminated the bulky deployment descriptors you'd see in typical J2EE applications, you can't help but think that the future of JSF will be in that direction.

-Cameron McKenzie
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic