What Is New in JSF 1.1
JSF 1.1 was primarily a maintenance release focused on stabilizing the initial 1.0 specification. It addressed key bugs and added clarifications to the API, making it more robust for production use.
| Category | Key Changes |
|---|---|
| Specification Clarifications | Refined the specification document to resolve ambiguities and improve readability. |
| API Refinements | Minor adjustments to the JSF API for better consistency and predictability. |
| Bug Fixes | Addressed a number of issues reported in the JSF 1.0 RI (Reference Implementation). |
| JSP Integration | Improved the integration and behavior of JSF components within JavaServer Pages. |
How did JSF 1.1 improve specification clarity?
The core goal of JSF 1.1 was to clean up the specification text itself. This meant going through the document and fixing sections that were unclear, contradictory, or ambiguous.
For developers, this resulted in a more predictable programming model. When the rules of the framework are well-defined, you spend less time debugging unexpected behavior and more time building features.
What were the main API tweaks?
JSF 1.1 introduced minor API refinements rather than sweeping new features. These changes were about making the existing APIs more consistent and logical.
In practice, this meant that code written for JSF 1.0 would largely work unchanged in 1.1, but the underlying platform felt more polished. It was about fixing the rough edges from the initial release.
Why was JSP integration a focus?
Since JSF 1.0 and 1.1 used JSP as their default view declaration technology, a stable integration was critical. This release worked out kinks in how JSF custom tags interacted with the JSP lifecycle.
This matters because any instability in the view layer directly causes bugs in page rendering. A smoother integration meant fewer headaches when designing pages with JSF components.
FAQ
Is JSF 1.1 a major feature release?
No, it's not. Think of it as a service pack for JSF 1.0. The focus was on bug fixes, clarifications, and stability, not on adding significant new functionality.
Is my JSF 1.0 application compatible with JSF 1.1?
Yes, absolutely. The changes were backward-compatible. You should be able to drop in the JSF 1.1 libraries without modifying your 1.0 code.
What is the most important reason to upgrade from 1.0 to 1.1?
Stability. If you were running into obscure bugs or unexpected behavior with the 1.0 RI, upgrading to 1.1 would likely resolve those issues.
Does JSF 1.1 introduce Facelets?
No, Facelets was not part of the official specification until later versions. JSF 1.1's view technology was still primarily JSP.
Where can I find the specific bugs that were fixed?
The exact list was tracked in the issue management system for the JSF Reference Implementation (RI). The specification itself outlines the general areas of improvement rather than individual bug numbers.