Skip to content

Document: Jakarta EE 11: Support Jakarta Server Faces 4.1 #7969

@volosied

Description

@volosied

OpenLiberty/open-liberty#25089

Differences between Jakarta Server Faces 4.1 and 4.0

Originally a Faces 5.0 release was planned, but was too ambitious. Instead, the scope was adjusted to deliver a minor 4.1 release focusing on general improvements and deprecations.

New Additions:

  • CDI events, @Initialized, @BeforeDestroyed, and @Destroyed now fire for build-in scopes (ViewScoped, FlowScoped)
  • It's now possible to inject Flow objects into backing beans using @Inject Flow currentFlow
  • A built-in jakarta.faces.convert.UUIDConverter is now provided via the API.
  • The jakarta.faces.context.ExternalContext.setResponseContentLengthLong() as been added.
  • The rowStatePreserved property is now supported by the ui:repeat tag, just as with h:dataTable.
  • The jakarta.faces.FACELETS_REFRESH_PERIOD default when ProjectStage is Development
  • The jakarta.faces.application.FacesMessage class now implements the equals(), hashcode(), and toString() methods. These are useful to allow FacesMessages to stored within HashMaps.
  • Generics were further incorporated throughout the API.

Deprecations:

  • Full State Saving (FSS) has been deprecated. This setting is enabled by either jakarta.faces.PARTIAL_STATE_SAVING or jakarta.faces.FULL_STATE_SAVING_VIEW_ID.
  • The jakarta.faces.event.PreDestroyCustomScopeEvent and jakarta.faces.event.PostConstructCustomScopeEvent classes have been deprecated. These were missed during the CustomScoped removal in Faces 4.0.
  • The unimplemented composite:extension tag as been deprecated.
  • All SecurityManager references within the API have been removed to align with the newer JDKs.

Metadata

Metadata

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions