[
https://issues.apache.org/jira/browse/MYFACES-4160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16183744#comment-16183744
]
Werner Punz edited comment on MYFACES-4160 at 9/28/17 6:38 AM:
---------------------------------------------------------------
Hi I am a little bit bound by other things this week, (one of them is to get
out another ext-scripting release), I will to get back to you sometime next
week.
I think AjaxResponse22 is not really workable code, I need to check it - it
should not have made it into the codebase, I think. But take this with a grain
of salt it has been a while.
In any way, the viewstate handling has been altered for jsf 2.3, we need to fix
this in our code, there was no fix without breaking jsf.js code because the old
viewstate handling was broken by design.
In the long run we should replace the existing javascripts since it is rather
old. There is a load of code in there which is obsolete:
Also we need to add Websockets, which is also part of the JSF 2.3 js part. (I
need to look into that)
a) We use our own class system based in prototype
b) We support stone old browsers, we should ramp it up to IE9 as baseline I
guess, I wonder if anyone still uses any IE below that in a corporate
environment?
c) We might rewrite the code in Typescript for maintainability reasons, this
would allow us to ramp up the Ecmascript level dynamically and also to switch
module systems on the fly (aka with ES6 a standardized module system was
finally introduced)
I have started to work on it on a github project this summer... but I never
publicly announced it since the entire thing is not in a representable state
yet.
What I would propose is following:
a) Fix the old codebase for JSF 2.3
b) Lets reimplement the stuff in Typescript with a bunch of helpers from modern
libs like a dom query engine and Promise shims and drop really old browser
support along the way - so that we can offer the new codebase sometime along
jsf 2.3.
c) Drop the old codebase for JSF 2.4
was (Author: werpu):
Hi I am a little bit bound by other things this week, (one of them is to get
out another ext-scripting release), I will to get back to you sometime next
week.
I think AjaxResponse22 is not really workable code, I need to check it - it
should not have made it into the codebase, I think. But take this with a grain
of salt it has been a while.
In any way, the viewstate handling has been altered for jsf 2.3, we need to fix
this in our code, there was no fix without breaking existing code.
In the long run we should replace the existing javascripts since it is rather
old. There is a load of code in there which is obsolete:
Also we need to add Websockets, which is also part of the JSF 2.3 js part. (I
need to look into that)
a) We use our own class system based in prototype
b) We support stone old browsers, we should ramp it up to IE9 as baseline I
guess, I wonder if anyone still uses any IE below that in a corporate
environment?
c) We might rewrite the code in Typescript for maintainability reasons, this
would allow us to ramp up the Ecmascript level dynamically and also to switch
module systems on the fly (aka with ES6 a standardized module system was
finally introduced)
I have started to work on it on a github project this summer... but I never
publicly announced it since the entire thing is not in a representable state
yet.
What I would propose is following:
a) Fix the old codebase for JSF 2.3
b) Lets reimplement the stuff in Typescript with a bunch of helpers from modern
libs like a dom query engine and Promise shims and drop really old browser
support along the way - so that we can offer the new codebase sometime along
jsf 2.3.
c) Drop the old codebase for JSF 2.4
> 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
> 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)
