[
https://issues.apache.org/jira/browse/MYFACES-4160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16183778#comment-16183778
]
Thomas Andraschko commented on MYFACES-4160:
--------------------------------------------
Sounds good werner!
Websockets are AFAICS already implemented by Leo.
I will check the issue today and also remove the duplicate AjaxResponse. I will
also check if we can easily remove sound of the codebase, which will result in
a smaller javascript for the client.
For 2.4, we should really reimplement it.
In PrimeFaces we have the same functionality as in the JSF API and the source
is really small and clean compared to the myfaces one:
https://github.com/primefaces/primefaces/blob/master/src/main/resources/META-INF/resources/primefaces/core/core.ajax.js
(NOTE: we even have some more features)
I'm not sure if we should Typescript for the reimplementation as i'm not sure
if we can easily integrate it in our maven builds (1-2 years ago there were no
good plugins available). I don't think we should require that a MF developer
should install gulp+nodejs+....
> ViewState not written for Ajax request
> --------------------------------------
>
> Key: MYFACES-4160
> URL: https://issues.apache.org/jira/browse/MYFACES-4160
> Project: MyFaces Core
> Issue Type: Bug
> Affects Versions: 2.3.0-beta
> Reporter: Thomas Andraschko
> Assignee: Werner Punz
> Fix For: 2.3.0
>
>
> If you run the application from MYFACES-4156 via mvn jetty:run, the
> viewStateId isn't rendered again after the first ajax request.
> Seems like FaceletViewDeclerationLanguage line 1910 should handle that but it
> skips.
> [~lu4242] Could you please check that?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
