File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
http://aspose.com/file-tools
Win a copy of Clojure in Action this week in the Clojure forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

JSF and AJAX are just opposite

 
ankur rathi
Ranch Hand
Posts: 3830
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
One (JSF) is evolved to eliminate JS and other uses JS extensively.

Right?
[ May 31, 2006: Message edited by: rathi ji ]
 
Jeff Albertson
Ranch Hand
Posts: 1780
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
How did you come to the conlusion that "JSF is evolved to eliminate JS"? Plenty of JSF components (see Tomahawk for example) generate heaps of JavaScript. The nice thing is that a web app developer can let the JSF implementation worry about most (but not all ) of the JS details. Nothing stops a JSF component from being implemented using AJAX.
 
ankur rathi
Ranch Hand
Posts: 3830
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Jeff Albertson:
How did you come to the conlusion that "JSF is evolved to eliminate JS"? Plenty of JSF components (see Tomahawk for example) generate heaps of JavaScript. The nice thing is that a web app developer can let the JSF implementation worry about most (but not all ) of the JS details. Nothing stops a JSF component from being implemented using AJAX.


I thought, JSF handle validation and conversion nicely (that usually done through JS) so...

:roll:
 
Jeff Albertson
Ranch Hand
Posts: 1780
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by rathi ji:


I thought, JSF handle validation and conversion nicely (that usually done through JS) so...

:roll:


Nothing stops you from mixing client-side validation into JSF. Iin any case, one need server-side validation because the client could be turning off JavaScript. Conversion, by definition, is done on the server side -- HTTP posts strings to you, not numbers and dates, for example!
 
ankur rathi
Ranch Hand
Posts: 3830
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Jeff Albertson:


Nothing stops you from mixing client-side validation into JSF. Iin any case, one need server-side validation because the client could be turning off JavaScript. Conversion, by definition, is done on the server side -- HTTP posts strings to you, not numbers and dates, for example!


Thanks Jeff for nice explaination.

 
Dave Boyd
Greenhorn
Posts: 10
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
if you ever wanted to check out the source that JSF procedures you may be shocked just how much javascript is used

just look at the command components for example
 
Sergey Smirnov
Ranch Hand
Posts: 167
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

Nothing stops you from mixing client-side validation into JSF. Iin any case, one need server-side validation because the client could be turning off JavaScript. Conversion, by definition, is done on the server side -- HTTP posts strings to you, not numbers and dates, for example!


I agree about "nothing stops...", but cannot see the special reason why the code of the validators should be duplicated. Having the javascript based validators was the only one choice in pre-AJAX era, because the server-side code was just unacceptable. In case of AJAX you have a chance to reuse the same code.

--
Sergey : https://ajax4jsf.dev.java.net
 
Don't get me started about those stupid light bulbs.
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic