JSF SOS

[Bess Moore]

Hi guys,

i really need your expertise in the JSF area, i am getting more confuse as days goes by.... help

In Whizlab question stated one of JSP drawback is it will have difficulties render JSF component in HTML.
And yet in JSF specification from Sun mentioned that JSF is build for Author who are non-programmer.

1. 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 thought to create the UI component or backing bean and etc need knowledge of java?

2. And if question asked to choose to develop a quicker way to develop a web application, given JSP and JSF how should we choose?

3. And when do we use jsf and ajax? like under what senario?

[Oleg Tikhonov]

Hello, according to your questions:
First of all, a JSF applications are built on top of the Servlet API, communicate via HTTP, and use a display technology like JSP (but not required). In addition, when we speak about JSF the following terms in mind: UI component, Renderer, Validator, Backing beans, Converters, Events and Listeners, Messages and Navigation.
RPL(Request Processing Lifecycle) -> JSF restores/creates view, translates the request parameters into GUI controls values, validates input, updates backing beans, invokes action listiners and finaly returns respons to the user.

2. And if question asked to choose to develop a quicker way to develop a web application, given JSP and JSF how should we choose?

IMHO, if you want develop your application "without bad smell" i would advise to choose JSF.

And when do we use jsf and ajax? like under what senario?

There are a lot of situations, i will try to cover some of them. When you need asynchronously communicate with server,
or any other business servises, you can send request to the server in order to retreive specific data, in other words
there is ability to send data between client and server. Another case, imagine that you have page with a lot of GUI components on it. To render this page each time when it's needed takes too much resourses, hence, to prevent updating a whole page you use Ajax that "wraped" in the components, for example.

Cheers,
Oleg.

[Bess Moore]

Thank you so much for your reply much appreciated

Oleg Tikhonov wrote:IMHO, if you want develop your application "without bad smell" i would advise to choose JSF.

Whizlab example
If we need to build something quick and there are some non Java resource and very limited resource on Java, give below (choose 2)
a. JSP
b. JSF
c. Pojo with JDBC
e. EJB

how should we choose?

[Cameron Wallace McKenzie]

of JSP drawback is it will have difficulties render JSF component in HTML.

I'm not sure what that means. Sometimes JSF components have problems being indexed by search engined, as with most scripted and Ajax based components, but that's about it.

JSF makes things easier for developers, supposedly. It is also tag based, so non-programmers are more comfortable and productive with it.

Don't forget who designed the exam. JSF is considered the future by Sun. At least, they're probably the biggest backers. JSF is probably a better technology on the exam than it is in real life.

-Cameron McKenzie

[J J Wright]

Don't forget who designed the exam. JSF is considered the future by Sun. At least, they're probably the biggest backers. JSF is probably a better technology on the exam than it is in real life.

That's quite a worrying statement. I decided not to use JSF in my assignment for the simple reason you can't bookmark JSF pages. How can you have a serious e-commerce application that doesn't allow customers to bookmark product pages?