Jakarta Faces
Jakarta EE specification for building component-based user interfaces for web applications
Jakarta Faces, formerly Jakarta Server Faces and JavaServer Faces (JSF) is a Java specification for building component-based user interfaces for web applications. It was formalized as a standard through the Java Community Process as part of the Java Platform, Enterprise Edition. It is an MVC web framework that simplifies the construction of user interfaces (UI) for server-based applications by using reusable UI components in a page.
JSF 2.x uses Facelets as its default templating system. Users of the software may also use XUL or Java. JSF 1.x uses JavaServer Pages (JSP) as its default templating system.
History
In 2001, the original Java Specification Request (JSR) for the technology that ultimately became JavaServer Faces proposed developing a package with the name javax.servlet.ui
In June 2001, JavaWorld would report on Amy Fowler's team's design of "the JavaServer Faces API" (also known as "Moonwalk") as "an application framework for creating Web-based user interfaces".
Developments
Facelets (which was designed specifically for Java Server Faces) was adopted as the official view technology for JSF 2.0. This eliminates the life-cycle conflicts that existed with JSP, forcing workarounds by Java developers.
The new JSF developments also provide wide accessibility to Java annotations such as @ManagedBean, @ManagedProperty and @FacesComponent that removes the need for faces-config.xml, in all cases except framework extension.
The public source identifies “Jakarta Faces” as jakarta EE specification for building component-based user interfaces for web applications. This brief keeps that definition visible, then builds a research path around Jakarta, Faces and specification.
Why this record matters
A short description can identify a subject without explaining its stakes. For “Jakarta Faces”, the useful work is to connect “jakarta EE specification for building component-based user interfaces for web applications” to the records capable of establishing context and consequence.
Place names and jurisdictional language are key evidence: both can reveal earlier catalogue descriptions and overlooked record series. The source revision retrieved here is dated Jul 6, 2026. The linked authority identifier is Q729427. None of the 4 selected statements returned an explicit reference. The first chronological checks are 2001.
A single description cannot reconcile every naming convention, rebuilding phase or administrative transfer associated with a place. The source lead contains qualifying language; that uncertainty should survive quotation, summary and reuse. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Treat names, boundaries and functions as historically changeable. Maps, plans, inventories and administrative records can clarify what the place meant at different dates.
- Historic place names
- Jurisdictional context
- Routes into maps and plans
Contemporary maps, plans, listed-building records, estate papers and the responsible local or national archive.
Three-step research path
- Establish the record: confirm the title “Jakarta Faces”, its source revision and the description used here.
- Expand the search: follow Jakarta Faces primary sources, Jakarta Faces archive and Jakarta research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “Jakarta Faces”?
- Which earlier names or jurisdictions may reveal additional records?
- What physical evidence or contemporary plan supports the description?
Search terms from this dossier
This entry incorporates text from “Jakarta Faces” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.