Bauke Scholtz

The `` implementation is by design already unidirectional, from server to client. The other way round should go via ``, primarily because of maintaining the JSF view state and HTTP...

+1 for the idea. Put it between INFO and WARN. Bump of ordinals of WARN and higher will however affect backwards compatibility on those who are comparing them with hardcoded...

Converters and validators are basically `@Dependent` in the context of the `UIComponent` referencing it. Converter and validator instances should not be saved in view state. Stateless converters can perfectly fine...

I can understand that. The recommended approach is however to make it transient and then lazily construct it in getter method. ``` public class SerializableBean implements Serializable { private transient...

If we're going to make the data models serializable then we should absolutely make sure that all request scoped state / "component scoped" state is marked `transient`, such as `ListDataModel#index`,...

+1 This indeed still needs to be crystallized. For the record this is the complete set of candiates currently still manually scanned by Mojarra: - FacesComponent.class - FacesConverter.class - FacesValidator.class...

Let's move to 5.0. This isn't just a 'maintenance' change, this will require spec changes as well. We should also take the opportunity to drop managed=true attribute. And for Mojarra,...

Technically speaking, you can achieve that by plugging in another RenderKit.

To be clear, this ticket is referring to `#{request}`. Had to read ticket thrice before I understood what you meant.

> It seems that in 2.3, **we removed #{request}**, when 2.3 mode is active and delegated to CDI. @arjantijms can you please check what happened in 2.3 and explain why...