This week's book giveaway is in the OCAJP 8 forum. We're giving away four copies of OCA Java SE 8 Programmer I Study Guide and have Edward Finegan & Robert Liguori on-line! See this thread for details.
One of JSP drawback if it will have difficulties render JSF component in HTML.
And in JSF specification from Sun mentioned that JSF is build for Author who are non-programmer.
So how does this work then? If it has difficult to render then how is non-programmer build this??? Is that just by adding Tag without actually see how it looks like?
I am so confuse
Welcome to the real world, it sucks, but you're gonna love it !!!
I think we have a little bit of (human) language confusion here, but I'll see if I can make things more clear.
JSF is not designed to be only for HTML. HTML is the most popular type of output from JSF, but JSF abstracts the rendering (output) part, so if you wanted to use it to produce WAP or some other non-HTML display language, you would simply have to supply WAP renderers for the items that you wanted to be output in WAP.
As part of this separation of function from display, the JSF view shouldn't have display-specific items mixed in with the JSF tags. That means specifically HTML.
In the real world, we get sloppy sometimes about that. You can use the <f:verbatim> element type to embed HTML in the JSF output, and in many cases, you can even skip the verbatim quoting and place raw HTML directly in the JSF source. I don't recommend it, but it can be done,
JSF is designed to be as close to a form-based Model/View/Controller architecture as you can get in an HTTP-based environment. Full M/V/C isn't possible, but JSF is "good enough". By separating the form (view) from the display control and data-mode/business backend, it's possible for someone who isn't a Java programmer to design JSF web pages - all they have to do is understand the use of the JSF tags.