|
The steps involved in the implementation of the content page descriptor are described below.
Change the extension of the html page to active page extension
There are many implementations and extensions to JSF, our discussion is on the standard or reference implementation.
The initial UI would be prepared as html or xhtml page. The page content source location and name would be reflected in the page-id, whereas the final page URL would be entered into the page-url entry in the page descriptor.
In the basic implementation, this would have the .jsp extension.
| This: | /pages/northStorm.html |
| becomes: | /pages/northStorm.jsp |
This is captured in the descriptor as shwon below
PAGE DESCRIPTOR |
id |
pages/northStorm.html |
page-url |
pages/northStorm.jsp |
template |
|
description |
|
Insertion of declaration and other necessary code segments
There are other declarations and tags that must be entered into the page, these are shown below:
<%@ taglib uri="http://java.sun.com/jsf/html" prefix="h" %>
<%@ taglib uri="http://java.sun.com/jsf/core" prefix="f" %>
<html>
<head>
<title>Index Page</title>
</head>
<body>
<f:view>
//.
</f:view>
</body>
</html>
With the change of extension the page would display within the dynamic page environment without dynamic contents.
The declaration on top <@ would import the JSF tag libraries.
The f:view tag is required, it establish the root of the component tree for JSF. All components used must be placed within the body of this tag.
For this descriptor, the id attribute establishes the identity of page within the specification, whereas the page-url establishes the final URL of the implemented page.
The template attribute captures the template page used by the page. Since the standard JSF using JSP does not have template features, there is no information provided on this. The standard template facility used with JSF is Facelet; this is covered in the dictionary entries for Seams Framework
id
page-url
description
template
|
Technologies
