Free tools Windows power users keep installed
One-click scans. No signup required.
“Put JSF to work” is a historical Java web-development tutorial, not a current Jakarta Faces setup guide. InfoWorld’s archive lists Derek Yang Shen’s article as published July 19, 2004, and describes it as a practical application built with JavaServer Faces (JSF), Spring Framework, and Hibernate. The archive does not identify the sample application or its dependency versions, so it cannot serve as a reliable, copy-and-paste recipe for a modern Java project.
What “Put JSF to work” is about
InfoWorld’s archive lists Derek Yang Shen’s “Put JSF to work” as a 28-minute article published July 19, 2004. Its stated aim is to build a real-world web application using three technologies: JavaServer Faces, Spring Framework, and Hibernate. The archived listing does not provide enough detail to establish the application’s domain, source code, setup sequence, or library versions. InfoWorld’s archive entry supports the article’s date and broad scope, but not a reconstruction of its implementation.
How the three technologies fit together
The combination represents three broad concerns in a Java web application: JSF provides the user-interface framework, Spring supplies application-level infrastructure and integration, and Hibernate handles object-relational persistence. This is a useful way to understand the stack’s intended shape, not a verified description of the exact classes or configuration used in Shen’s tutorial.
JSF handles the web interface
JSF is a component-based, event-driven framework for building server-rendered interfaces. A request is routed to a view, whose components can be associated with application data and behavior. The Mojarra JSF 2.3 documentation describes how FacesServlet mappings route requests to Facelets views, including prefix, suffix, and exact mappings in that release; those details are specific to JSF 2.3, not a current Jakarta Faces configuration reference. Mojarra JSF 2.3 documentation
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Spring provides application integration
Spring can be used alongside JSF, but its own version 6.0.6 reference characterizes Spring’s JSF integration as primarily useful for migration and says that support is no longer actively evolved. The same reference describes JSF as part of the Jakarta EE umbrella and notes that it can be used with Tomcat. These are points from that specific Spring reference; check documentation matching the versions and runtime you intend to use. Spring Framework 6.0.6 JSF reference
Hibernate handles persistence
Hibernate is the persistence technology named in the archive description. The available archive listing does not say how the tutorial maps data, manages transactions, or connects Hibernate to Spring. Those implementation details should not be inferred from the title alone.
Rank #2
Is the old tutorial useful for a new project?
It can be useful as a historical example of how developers combined a server-side UI framework, application infrastructure, and persistence. It should not be treated as a current dependency recipe: the article is from 2004, its versions are not established by the archive, and Spring’s cited 6.0.6 documentation says its JSF support is not actively evolved.
| Use case | How to treat the tutorial |
|---|---|
| Understanding a legacy application | Use it as historical context, then inspect that application’s actual source, configuration, runtime, and library versions before making changes. |
| Starting a new JSF-based application | Choose compatible current platform and library releases from their official documentation. Do not assume the tutorial’s configuration or Spring integration is an appropriate default. |
| Learning the architecture | Use the named stack to understand the separation of interface, application integration, and persistence, while keeping the article’s unverified implementation specifics distinct from that general model. |
A practical way to approach a JSF application today
The exact steps depend on the JSF generation, Java runtime, deployment target, and versions of the application frameworks. Oracle’s JDeveloper guides illustrate one version-specific workflow: create a web application, build JSF/Facelets pages, connect business services through backing beans and data binding, configure resources, then run the pages. The 12.2.1.3 and 12.2.1.4 guides document those JDeveloper-era tools and assumptions; they are examples, not universal instructions for current projects. Oracle JDeveloper 12.2.1.3 guide · Oracle JDeveloper 12.2.1.4 guide
- Identify the Java runtime, JSF or Jakarta Faces generation, Spring release, Hibernate release, and deployment environment required by the project.
- Confirm compatibility across those versions using their official documentation before adopting configuration or code from an older example.
- For an existing application, let its actual source and deployment configuration—not the 2004 archive description—determine the implementation details.
What the related historical examples show
JSF views are not limited to one markup style. Oracle’s May 2014 article describes using HTML5 components in JSF views, server-side templates, and examples involving WebSocket and JSON-P. It demonstrates interoperability in that period’s Java EE context; it does not establish a current best practice or the compatibility of those examples with present-day framework releases. Oracle’s 2014 “HTML5 and JSF” article
Quick Recap
Best Value
Rank #4
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
