in our organisation we have to use JSF 2.0 application over SSL-Gateway. This gateway passes through only standard HTTP Headers, therefore JSF header "Faces-Request" is deleted from HTTP Request. JSF can not recognize AJAX request and it makes this requests unable to work.
...skipped... javax.faces.partial.ajax = true
As workaround to our problem I have written my own implementation of PartialViewContext which overwrites isPartialRequest and isAjaxRequest methods. New methods use "javax.faces.partial.ajax" instead of "Faces-Request" to identify AJAX request.
Is this eligible solution? Is "javax.faces.partial.ajax" parameter just additional flag for AJAX request or it has particular meaning? Can this workaround have unwanted side effects?
We are using Websphere AS 8 with MyFaces JSF2 implementation.
Not really a question anyone but you can answer. First of all lets get out in the open what this is: its not a solution, its a hack to work around the fact that you have a gateway configured in such a way that it basically makes it impossible for you to properly use a framework like JSF.
How do you feel about implementing a hack and breaking the specification? Would you put something like that in production? Do you like to live with absolutely no guarantee that any future version of MyFaces or the JSF specification is going to be compatible with your hack? I wouldn't, but I can't speak for you.