Did you try to use the regular h:commandButton or h:commandLink in this situation?
If Cookies are turn on, they are used. Otherwise, the URL postfix is used.
We checked this case on our side. The JSF application returns back to normal is the Cookies for the same domain are cleaned up manually in the browser.
Thanks for the comment Sergey.
JSF if properly working, but Ajax4JSF isn't.
I've tried with Glassfish, which I think that does not use Tomcat, and the same thing happens.
In fact the URL rewriting is also working, I get the following URL:
And all the pages are displayed as they are supposed, but those ones using Ajax4JSF doesn't load the Ajax4JSF Script: "org.ajax4jsf.framework.ajax.AjaxScript.jsf" so I get the following error:
syntax error [Break on this error] <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.or...
Regarding the first issue, I believe Glassfish is built on top of TomCat.
Regarding the ajax is not defined issue, I am using Glassfish also and had the same issue for my j2ee application where the ajax script pointer was not getting rendered. It was working correctly in a web app that I had also deployed on Glassfish, so I copied the pointer, modified it to point to my context path, and that got rid of the a4j is not defined errors.
I'm using SUN RI, but you probably can do something similar ...
Thank you wbossons,
I don't know the ui:script TAG, I'm using the 'ui' prefix for Facelets and I think that the 'script' tag isn't in it.
By the way, I managed to solve the issue with your hint. The problem is that Ajax4JSF is attaching the Ajax script in the following way:
While, as it is a '.jsf' file and no cookies are used to track sessions, the web server needs the session ID at the end of the URL:
So that was my solution, add the ajax4JSF script with the session ID.
Again, thank you very much for your help.