-
Notifications
You must be signed in to change notification settings - Fork 55
Open
Description
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@Destroyednow 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.UUIDConverteris now provided via the API. - The
jakarta.faces.context.ExternalContext.setResponseContentLengthLong()as been added. - The
rowStatePreservedproperty is now supported by theui:repeattag, just as withh:dataTable. - The
jakarta.faces.FACELETS_REFRESH_PERIODdefault when ProjectStage is Development - The
jakarta.faces.application.FacesMessageclass now implements theequals(),hashcode(), andtoString()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_SAVINGorjakarta.faces.FULL_STATE_SAVING_VIEW_ID. - The
jakarta.faces.event.PreDestroyCustomScopeEventandjakarta.faces.event.PostConstructCustomScopeEventclasses have been deprecated. These were missed during the CustomScoped removal in Faces 4.0. - The unimplemented
composite:extensiontag as been deprecated. - All SecurityManager references within the API have been removed to align with the newer JDKs.
Reactions are currently unavailable