|
|
Page 1 of 27 articles
|
|
UI frameworks and JavaServer Faces
The arrival of JSF should not cause you to abandon existing UI frameworks. The good news is that JSF is perfectly capable of working in conjunction with these frameworks, and has in fact been designed with easy integration in mind. Take a look at how JSF can be used in conjunction with existing frameworks, as an enhancement, not a potential replacement.
|
JSF Navigation by Examples
The JavaServer Faces (JSF) Navigation Framework provides navigation rules that allow you to define navigation from view to view (mostly JSP pages) in a Web application. These navigation rules are defined in JSF configuration files along with other definitions for a JSF application. Usually, this file is named faces-config.xml. However, you can assign any other name and even use more than one file to store JSF configuration data.
|
|
|
Creating JSF Custom Components
This article illustrates how to build custom components for use in web applications based on JavaServer Faces (JSF). While JSF comes with a standard set of components, one of the most-publicized features is the easy addition of new components. In this article, you will see just how easy it is to create new components that are fully functional and integrated into your web applications. Specifically, this article will show how to develop a component that allows users to enter valid credit card numbers.
|
Handling Events in JavaServer Faces, Part 1
Editor's note: O'Reilly's JavaServer Faces offers developers a guide to learning how to use the JSF framework to build web applications. In this excerpt from the book, author Hans Bergsten looks at the JSF event model, using examples to help explain what's going on "under the hood." Next week, in part two of this excerpt, Hans implements event handling for parts of the sample application discussed here.
|
Handling Events in JavaServer Faces, Part 2
Editor's note: The JSF model has the same look and feel as the event model used for standalone applications, but because user actions in JSF take place in a client separated from the server, delays occur in the delivery of some types of events until a new connection is established. In last week's part one of this two-part excerpt from JavaServer Faces, author Hans Bergsten provided examples to show how JSF deals with this difference, by using a strict request processing lifecycle. Here in part two, Hans implements event handling for parts of the sample application discussed in part one.
|
Understanding JavaServer Faces
This article examines JSF technology in both the business and technical horizons. You will be presented with the benefits of JSF and a scenario demonstrating the JSF support in the IBM WebSphere Studio Application Developer product.
|
JavaServer Faces, Web Applications Made Easier
JavaServer Faces (JSF) attempts to standardize the way we develop Java Web applications and provides a set of rich ready-to-use UI components. In this article, Mike Houghton will discuss the JSF technology, what's right, what's wrong and why it's necessary.
|
Q&A: JavaServer Faces
Sun engineers Mimi Hills, Tony Ng, and Ed Burns talk about the importance of JavaServer Faces in today's programming environment and how developers can best utilize it. Hills and Ng are software engineering managers in Sun's Java Web services group. Ng is also the manager of the JavaServer Faces team. Burns leads the team developing the specification for the JavaServer Faces project.
|
JavaServer Faces (JSF) vs Struts
My JSF article series and Meet the Experts appearance on IBM developerWorks received a lot of feedback. I would have to say, the most common question or feedback came along the lines of comparing Struts to JSF.
|
|
|
|
Next>> |