[
https://issues.apache.org/jira/browse/MYFACES-4160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16184880#comment-16184880
]
Thomas Andraschko commented on MYFACES-4160:
--------------------------------------------
Hmm, i'm really not sure about Typescript if it isn't easy. I think we can do a
good implementation also without typescript but lets discuss this for 2.4.
In PrimeFaces jQuery is used, yep. But i think the DOM manipulation is not sooo
hard for the ajax engine because we only need to support newer browsers and not
IE6 or 7 anymore.
Not sure about the AJAX request/response-handling, i'm jQuery user since almost
many years.
I would be great great if you could take care of it. I checked the base ~2
hours today and it's really hard to understand.
Also i'm not sure if AjaxResponse or AjaxResponseJSF22 is the correct one. We
really need to delete one of both and do a cleanup.
Not sure why this worked in MF2.2 - Maybe AjaxResponseJSF22 was used?
Do we need to support porlets? We have there some JS configs to update all
forms or not.
Porlets have some namespacing for the clientIds - which is currently also not
implemented on the server side. So not sure if we should care of it.
See:
https://github.com/ngriffin7a/primefaces/blob/master/src/main/resources/META-INF/resources/primefaces/core/core.ajax.js#L369
https://github.com/primefaces/primefaces/blob/master/src/main/java/org/primefaces/context/PrimePartialResponseWriter.java#L267
> 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)
