[
https://issues.apache.org/jira/browse/MYFACES-4160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16183934#comment-16183934
]
Werner Punz edited comment on MYFACES-4160 at 9/28/17 10:02 AM:
----------------------------------------------------------------
Well you can remove parts of it out of the box... There is an internal switch
to my knowledge which switches between xhr indirections, IE7 and older uses the
old xhr mechanism, and newer browser switch to the standardized xhr object -
there is no browser anymore which uses a non standardized xhr system,
since IE6 is absolutely dead by now.
I think I have the same switch also for the domUtils, but I need to check this
first.
As for the typescript maven integration i need to check the state of things
out. I would prefer typescript over pure javascript due to the typing and
really excellent syntax, as well as the possibility to change module systems
and es levels on the fly. If possible I would not go the
pure Javascript route anymore.
Btw. there is an excellent client side plugin for maven which installs the
entire npm toolchain during the build temporarily. This might be the way to go.
After all you need the typescript compile anyway only during development, the
javascripts are then checked in and do not need any further processing by maven
during the normal builds. We probably can add it to a dev profile or
dev-javascript profile.
was (Author: werpu):
Well you can remove parts of it out of the box... There is an internal switch
to my knowledge which switches between xhr indirections, IE7 and older uses the
old xhr mechanism, and newer browser switch to the standardized xhr object -
there is no browser anymore which uses a non standardized xhr system,
since IE6 is absolutely dead by now.
I think I have the same switch also for the domUtils, but I need to check this
first.
As for the typescript maven integration i need to check the state of things
out. I would prefer typescript over pure javascript due to the typing and
really excellent syntax, as well as the possibility to change module systems
and es levels on the fly. If possible I would not go the
pure Javascript route anymore.
Btw. there is an excellent client side plugin for maven which installs the
entire npm toolchain during the build temporarily. This might be the way to go.
> 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)
