[ 
https://issues.apache.org/jira/browse/MYFACES-4160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16185522#comment-16185522
 ] 

Werner Punz commented on MYFACES-4160:
--------------------------------------

Re portlets, this config entry is a helper to fix the broken viewstate handling 
of jsf 2.0-2.2, since it now is fixed in 2.3 it will go away.
I will take over the issue, but I wont be able to do it before next week.

And yes, if we baseline for IE9 we can move a lot of the query stuff to 
domNode.querySelectorAll. As I said about 40-50% of the existing code simply is 
there
to bypass and fix bugs of by now dead browsers, so after the release we are 
going to clean this all up one way or the other.
As I said
My preference would be:

a) Typescript, that can be discussed - it is just that I prefer it over plain 
javascript because then we can move Ecmascript levels and module systems on the 
fly
and the syntax is way cleaner and nicer, the maven integration should not pose 
to much of a problem - but that needs to be discussed

b) Promises to handle the entire ajax cycle in a sanmer manner, more or less 
like jquery allows it and other frameworks.

c) A thin query layer over document.querySelectorAll  to get rid of the 
domutils class, ideally would be jquery because this delivers in some areas 
where plain dom lacks, like outerHTML, a promise layer over ajax, some fixes 
for browser incompatibilities etc... but that is out of the question, we cannot 
bundle such a lib or require such a lib. Primefaces has an easier stand here, 
because it is a third party lib not a core lib.

And then the code should become clean and maintainable without all the legacy 
junk. 


> 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)

Reply via email to