With support for these techniques, this newest version of the Java component UI framework enables developers to build truly dynamic web pages simply and easily.
At the highest level, JSF technology provides an API for creating, managing, and handling UI components and a tag library for using components within a web page. The JSF 2.0 release simplifies the web developer’s life by providing the following:
- Reusable UI components for easy authoring of web pages
- Well defined and simple transfer of application data to and from the UI
- Easy state management across server requests
- Simplified event handling model
- Easy creation of custom UI components
For GET requests and Ajax integration, we need to drill down into JSF 2.0’s support, as well as the productive features that this support makes possible. The demo application is an online quiz that allows a registered user to answer five simple questions that test his or her general knowledge. Towards the end of the quiz, the application displays the score.
Using GET Requests in JSF 2.0
To support GET requests, JSF 2.0 introduced the concept of View Parameters. View Parameters provide a way to attach query parameters to URLs. You use the tag <f:viewParam> to specify the query parameters.
Take this code for example:
<f:metadata>
<f:viewParam name=”previousScore” value=”#{recordBean.oldScore}” />
</f:metadata>
In this example, the value of the parameter previousScore will be automatically picked up and pushed into the property oldScore of the recordBean. So, when a request like this comes for a URL:
displayData.jspx?previousScore=10
To support GET requests, JSF 2.0 introduced the concept of View Parameters. View Parameters provide a way to attach query parameters to URLs. You use the tag <f:viewParam> to specify the query parameters.
Take this code for example:
<f:metadata>
<f:viewParam name=”previousScore” value=”#{recordBean.oldScore}” />
</f:metadata>
In this example, the value of the parameter previousScore will be automatically picked up and pushed into the property oldScore of the recordBean. So, when a request like this comes for a URL:
displayData.jspx?previousScore=10
The value of the bean property oldScore will be set to 10 when the request is processed, which avoids manually setting the value or using a listener. Another interesting point to notice is that like any other component the tag <f:viewParam> supports conversion and validation. Hence, there is no need for separate conversion/validation logic.
The new tags in JSF 2.0 related to support for the GETrequest.
h:button :- Renders a button that generates a GET request without any handcoding of URLs
h:link :- Renders a link that generates a GET request without any handcoding of URLs
h:outputStylesheet :- Refers to a CSS resource
h:outputScript :- Refers to a JavaScript resource
f:event :- Registers a specification-defined or a user-defined event
f:ajax :- Enables associated component(s) to make Ajax calls
f:metadata :- Declares the metadata facet for this view
f:viewParam :- Used in to define a view parameter that associates a request parameter to a model property
f:validateBean :- Delegates the validation of the local value to the Bean Validation API
f:validateRegex :- Uses the pattern attribute to validate the wrapping component
f:validateRequired :- Ensures the presence of a value
Bookmarking Support
Because all JSF 1.x interactions with the server use only HTTP POST requests, those JSF versions don’t support bookmarking pages in a web application. Even though some tags supported the construction of URLs, it was a manual process with no support for dynamic URL generation. JSF 2.0’s support for HTTP GET requests provides the bookmarking capability with the help of new renderer kits.
A new UI component UIOutcomeTarget provides properties that you can use to produce a hyperlink at render time. The component allows bookmarking pages for a button or a link.
The two HTML tags that support bookmarking are h:link and h:button. Both generate URLs based on the outcome property of the component, so that the author of the page no longer has to hard code the destination URL. These components use the JSF navigation model to decide the appropriate destination.
Take the following code for example:
<h:link outcome=”login” value=”LoginPage” >
<f:param name=”Login” value=”#{loginBean.uname }” />
</h:link>
This bookmarking feature provides an option for pre-emptive navigation (i.e., the navigation is decided at the render response time before the user has activated the component). This pre-emptive navigation is used to convert the logical outcome of the tag into a physical destination. At render time, the navigation system is consulted to map the outcome to a target view ID, which is then transparently converted into the destination URL. This frees the page author from having to worry about manual URL construction.
Support for Ajax
The default implementation provides a single JavaScript resource that has the resource identifier jsf.js. This resource is required for Ajax, and it must be available under the javax.faces library. The annotation@ResourceDependency is used to specify the Ajax resource for the components, the JavaScript function jsf.ajax.request is used to send information to the server in an asynchronous way, and the JavaScript function jsf.ajax.response is used for sending the information back from the server to the client.
On the client side, the API jsf.ajax.request is used to issue an Ajax request. When the response has to be rendered back to the client, the callback previously provided by jsf.ajax.request is invoked. This automatically updates the client-side DOM to reflect the newly rendered markup.
The two ways to send an Ajax request by registering an event callback function are:
- Use the JavaScript function jsf.ajax.request
- Use the <f:ajax> tag
JavaScript Function jsf.ajax.request
The function jsf.ajax.request(source, event, options) is used to send an asynchronous Ajax request to the server. The code snippet below shows how you can use this function:
<commandButton id=”newButton” value=”submit”
onclick=”jsf.ajax.request(this,event,
{execute:’newButton’,render:’status’,onevent: handleEvent,onerror: handleError});return false;”/>
</commandButton/>
The first argument in the function represents the DOM element that made an Ajax call, while the second argument (which is optional) corresponds to the DOM event that triggered this request. The third argument is composed of a set of parameters, which is sent mainly to control the client/server processing. The available options are execute, render, onevent, onerror, and params.
<f:ajax> Tag
JSF 2.0 enables page authoring with <f:ajax>, which is a declarative approach for making Ajax requests. You can use this tag instead of manually coding the JavaScript for Ajax request calls. This tag serves two roles, depending on the placement. You can nest it within any HTML component or custom component. If you nest it with a single component, it will associate an Ajax action with that component.
The <f:ajax> tag has four important attributes:
- render – ID or a space-delimited list of component identifiers that will be updated as a result of the Ajax call
- execute – ID or a space-delimited list of component identifiers that should be executed on the server
- event – The type of event the Ajax action will apply to (refers to a JavaScript event without the on prefix)
- onevent – The JavaScript function to handle the event
Consider the following code from the login page of the online quiz application. The code validates the input of the email field by sending an Ajax call for every keystroke. The validation is done by a managed bean method that acts as a value change listener.
<h:inputText label=”eMail ID” id=”emailId” value=”#{userBean.email}” size=”20″
required=”true” valueChangeListener=”#{userBean.validateEmail}”>
<f:ajax event=”keyup” render=”emailResult”/>
</h:inputText>
…
<h:outputText id=” emailResult” value=”#{userBean.emailPrompt}” />
Using Ajax to Validate the Input: The online quiz application validates email field input by sending an Ajax call for every keystroke.
Here, <f:ajax> is nested within the emailId inputText component. For every keyup event that is generated, an Ajax call is sent to the server, which invokes the valueChangeListener. By default, the component in which the tag is nested is executed on the server. So, the execute attribute is not specified. Also, for an input component, the default event is valueChange, so the event attribute is also not used. The render attribute indicates that the outputText component emailResult should be updated after the Ajax call.
If you place this tag around a group of components, it will associate an Ajax action with all the components that support the events attribute.
<f:ajax event=”mouseover”>
<h:inputText id=”input1″ …/>
<h:commandLink id=”link1″ …/>
</f:ajax>
In this example, input1 and link1 will exhibit Ajax behavior on a mouseover event.
<f:ajax event=”mouseover”>
<h:inputText id=”input1″ …>
<f:ajax event=”keyup”/>
</h:inputText>
<h:commandLink id=”link1″ …/>
</f:ajax>
In this example, input1 and link1 exhibit Ajax behavior on keyup and mouseover events, respectively.
Using the Ajax tag enhances the markup of the associated component to include a script that triggers the Ajax request. This the page author to issue Ajax requests without having to write any JavaScript code.
These new features enable developers to build truly dynamic web pages simply and easily.
http://www.developer.com
http://www.all1sourcetech.com
