nimo23

>I think this original ticket was just about changing the rendering of the label. Yours is considerably more complex with multiple facets. Ok, I open a new issue for this....

I think, it's not really required. We can easily turn a set to a list manually (e.g. `new ArrayList(mySet);`) and use this list for `p:autoComplete`.

>BWT, if possible to write the facelet template with the popular frameworks directly, such as React components, and make the Faces managed beans/components(CDI beans) in the background worked as React...

>The implementation is by design already unidirectional, from server to client. I think, for use cases needing only unidirectional connections, SSE has some benefit over websocket connections (e.g. no websocket-reconnections,...

>The implementation is by design already unidirectional, I think, it would be better to _re-implement_ the `f:push` to use SSE instead of WebSocket. It would not only fit better to...

>you also have e.g. to reinit the JS widget in PF Yes, however. Maybe "faces api" could introduce a new **synchronization contract** to client libs like PF. I think https://github.com/jakartaee/faces/issues/1598#issuecomment-1047152803...

>IMO it would be MUCH easier to e.g. partially use a PrimeVue DataTable inside your JSF view Yes, _today_ (with the current faces api), it would be much easier to...

I come up with the following idea: JSF can renew all of its "client-side synchronization" (_which actually works by replacing HTML pieces within HTML pages_) with the standardized **WebComponents**. JSF...

Suggestion: Provide 3 states when dealing with Java Numbers: **1. Config with `WRITE_NAN_AS_STRINGS`** ``` // uses strings for "NaN", "+Infinity", "-Infinity" // instead of throwing NumberFormatException when (de)serializing Maps.of(JsonGenerator.WRITE_NAN_AS_STRINGS, true);...

Something like this **to auto register adapter** would be nice: ``` @JsonBAdapter public class UserAdapter implements JsonbAdapter { @Override public JsonObject adaptToJson(User user) throws Exception { return Json.createObjectBuilder() ... .build();...