[
https://issues.apache.org/jira/browse/MYFACES-4160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16192522#comment-16192522
]
Werner Punz edited comment on MYFACES-4160 at 10/5/17 6:38 AM:
---------------------------------------------------------------
Just wanted to give a status update, I have implemented basically the new
response behavior but I need to write some tests first before dropping the code
into the myfaces codebase.
The entire viewstate handling has become tighter, it is just basically
determine the viewroot if an updates id is given and then update all forms
under this viewRoot as usual with the given artifact (clientWindowId, Viewstate
etc...)
So all this special handling regarding issuing element, rendered fragment, our
special handling for non portlet multiform environments all gone.
This is good news because I was really unhappy with this part due to the fixes
and workarounds it had, caused by the broken jsf 2.0-2.2 spec in this area.
(God knows I reported the spec bug for JSF 2.0)
Expect the code if all goes well (I need to recheck the spec if I have covered
all, for now I was using the Tijms weblog to get a quick grasp) late weekend,
monday.
Once this is implemented I will start the discussion on the mailing list on how
we proceed with the reimplementation, for now I have two options use
Typescript, a language which I am very familiar with due to my daywork, also we
could use the Kotlin -> Javascript crosscompiler which I need to evaluate. I do
not want to go to pure javascript again, it has so many advantages to use a
better language especially since we cannot target ES6 anyway.
was (Author: werpu):
Just wanted to give a status update, I have implemented basically the new
response behavior but I need to write some tests first before dropping the code
into the myfaces codebase.
The entire viewstate handling has become tighter, it is just basically
determine the viewroot if an updates id is given and then update all forms
under this viewRoot as usual with the given artifact (clientWindowId, Viewstate
etc...)
So all this special handling regarding issuing element, rendered fragment, our
special handling for non portlet multiform environments all gone.
This is good news because I was really unhappy with this part due to the fixes
and workarounds it had, caused by the broken jsf 2.0-2.2 spec in this area.
(God knows I reported the spec bug for JSF 2.0)
Expect the code if all goes well (I need to recheck the spec if I have covered
all, for now I was using the Tijms weblog to get a quick grasp) late weekend,
monday.
Once this is implemented I will start the discussion on the mailing list on how
we proceed with the reimplementation, for now I have two options use
Typescript, a language which I am very familiar with due to my daywork, also we
could use the Kotlin -> Javascript crosscompiler which I need to evaluate. I do
not want to go to pure javascript again, it has so many advantages to use a
better language.
> 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)
