Patterns: Implementing Self-Service in an SOA Environment

Chapter 9. JSF front-end scenario 289

Through out this chapter we have seen multiple examples of navigation rules,

managed bean declarations, validator declarations, and so forth that are stored

in the file. For the most part, Rational Software Architect takes care of creating

and updating web-config.xml based on information we entered using the various

wizards. However we encourage you to look at the examples we provide and

understand the general structure of the file. It is not unusual for a designer or

developer to make small manual changes to the file for things that are not

supported by wizards. The custom e-mail validator in 9.4.6, “Implementing input

validation” on page 280 is one such example.

9.6 System management

As we have explained, the JavaServer Faces framework does not require special

resources to be allocated and maintained on the server. Moreover, once the JSP

files, managed beans, and configuration information is processed by the

application server, it breaks down into well known J2EE components such as

servlets, java classes, HTTP session data, and so forth. The display code which

eventually gets forwarded to the user browser, is a standard combination of

HTML and JavaScript. Therefore, there are no significant system management

considerations particular to the JSF technology.

9.7 For more information

For more information about the topics covered in this chapter see:

򐂰 WebSphere Studio 5.1.2, JavaServer Faces and Service Data Objects,

SG24-6361

򐂰 Rational Application Developer V6 Programming Guide, SG24-6449

򐂰 WebSphere Application Server V6 System Management and Configuration

Handbook, SG24-6451

򐂰 IBM developerWorks

http://www.ibm.com/developerWorks

򐂰 Sun JavaServer Faces Technology Page

http://java.sun.com/j2ee/javaserverfaces/index.jsp

290 Patterns: Implementing Self-Service in an SOA Environment