What Is New in PrimeFaces 11.0
PrimeFaces 11.0 is a significant release that modernizes the framework by aligning with the latest Java EE and JSF standards. It brings a host of new components, major upgrades to existing ones, and a focus on improving developer experience and performance.
| Category | Key Highlights |
|---|---|
| New Features | New components: Signature, Stepper, ImageCompare. New themes: Lara, Aura. |
| Improvements | Major upgrades to Charts, Editor, and FileUpload components. Full compatibility with JSF 2.3 and 4.0. |
| Deprecations | Legacy themes (e.g., Omega) and deprecated methods have been removed. |
| Bug Fixes | Numerous fixes across the component suite for improved stability. |
What are the major component upgrades?
The Charts, Editor, and FileUpload components received substantial rewrites. The Charts now use a modern, configurable API that is much easier to work with compared to the old model.
The Editor component was completely replaced with a new implementation. In practice, this means better performance and a more modern feature set that developers expect from a rich text editor.
FileUpload was refactored for better efficiency. This matters because file handling is a common task, and the new implementation is more robust and easier to integrate into complex forms.
What new components were introduced?
PrimeFaces 11.0 adds three new components to its arsenal. The Signature component captures smooth, vector-based signatures as input.
The Stepper component provides a visual guide for users to navigate through a sequence of steps in a form or workflow. It's great for breaking down complex data entry tasks.
ImageCompare allows users to interactively compare two images by sliding a divider between them. This is perfect for showcasing before-and-after scenarios directly in the UI.
How does the theming system change?
The legacy themes, including Omega and its variants, have been removed. They are replaced by the new Lara and Aura design families, which offer a more modern and sleek appearance.
Lara is the new default theme, providing a clean and professional look out of the box. The new theming is built with design tokens, making customization more systematic and less error-prone than overriding old CSS.
What is the compatibility story for JSF and Java?
This release is fully compatible with JSF 2.3 and the new Jakarta EE 9.1, which uses the jakarta.* namespace. This is a crucial update for teams moving their applications from Java EE to Jakarta EE.
If you're still on an older JSF version, you'll need to upgrade your application's dependencies to use this version of PrimeFaces. The framework no longer supports the legacy javax.faces.* namespace.
FAQ
Is PrimeFaces 11.0 a breaking change?
Yes, it can be. The removal of deprecated themes and the requirement for JSF 2.3+/Jakarta EE 9.1 means existing applications might need dependency updates and theme migrations.
How do I migrate my Charts from the old model?
You'll need to rewrite your chart code. The old model was removed entirely. The new API is more powerful but requires adopting the new configuration approach documented in the showcase.
What should I use instead of the Omega theme?
Migrate to the new Lara theme. It's the new default and provides a modern replacement. Check the theme documentation for customization details.
Does the new FileUpload component work differently?
Yes, it was refactored. The core functionality is the same, but the internal implementation is more efficient. You should test your file upload logic after upgrading.
Can I use this with Java EE 8?
No. PrimeFaces 11.0 requires the jakarta.* namespace introduced in Jakarta EE 9 and JSF 2.3. You must upgrade your application server and dependencies accordingly.