Hi, Thank you very much for the fix Werner. I took the latest core today and built it and tested from payara without any config changes. Found ajaxresponse22.js deleted and ajaxresponse.js changed. And the behavior of repeated ajax calls is same. Can we have the config changes exactly if any in this manner? I checked 4160 and quickly not make out the config changes. <context-param> <param-name>xyz</param-name> <param-value>abc</param-value> </context-param> Thanks & Regards,Dora Rajappan. On Sunday, October 8, 2017, 7:39:48 PM GMT+5:30, Werner Punz <werner.p...@gmail.com> wrote: No sync with Mojarra I have discussed that a while ago. The problem is a licensing problem. Mojarra basically can use our code but not vice versa, because the CDDL cannot be implemented in ASF2 code.
The ASF2 license is a very liberal license, but due to the fact that it is so liberal, it is impossible to integrate less liberal code in our codebase. As for your repeated Ajax problems MYFACES-4160 that is a really old spec bug which reared its ugly head in multiform scenarii. I worked around that by providing a special config param. With JSF 2.3 it finally will be fixed. Werner Am 06.10.17 um 11:59 schrieb Dora Rajappan: > Thanks for detailing the future of browser and how jsf cope up with it. > > I was using mojarra for my application and the commandLink was not > working due to script problem. > So I switched to myfaces and we got some problem with repeated ajax > calls. (Myfaces 4160). > > Are we syncing with mojarra regarding the technology to be used with the > jsf.js, entire scripting arena. > Not sure spec say anything about the technology used for scripting. > > Thanks & Regards, > Dora Rajappan.
