jsf-2.2

We are using JavaServer Faces 2.2 (Mojarra 2.2.1) in our project. I noticed something odd. On a page called reporting.xhtml where I use f:metadata with the new f:viewAction my browser, Safari in this case, shows the following query string: reporting.jsf?jftfdi=&jffi=reporting%3Ffaces-redirect%3Dtrue What wizardry is this? What are the parameters jftfdi and jiffi doing? What is their purpose? It's part of the new JSF 2.2 feature as described by spec issue 949 . Basically, it enables JSF to identify the client window. It's basically the same as cid in CDI's @ConversationScoped and windowId in

I have this fragment: <h:form id="form"> <!-- other content --> <p:panel id="panel" header="test"> <p:inputText id="input1" value="#{viewScope.prop1}" required="true" /> <p:commandButton id="button1" process="@form" update="@form @widgetVar(dialog)" oncomplete="PF('dialog').show()" value="ok" /> </p:panel> <!-- other content --> </h:form> <p:dialog id="dialog" header="dialog" widgetVar="dialog" modal="true"> <h:form id="form2"> <p:inputText id="input2" value="#{viewScope.prop1}" required="true" /> <p:commandButton id="button2" process="@form" update="@form" value="ok" /> </h:form> </p:dialog>

Caution : Although this question covers long textual information with a mess of Java code snippets, it is merely targeted to JavaScript/jQuery and a bit of PrimeFaces stuff (just <p:remoteCommand> ) as mentioned in the introductory part in the beginning. I am receiving a JSON message from WebSockets (Java EE 7 / JSR 356 WebSocket API) as follows. if (window.WebSocket) { var ws = new WebSocket("wss://localhost:8181/ContextPath/AdminPush"); ws.onmessage = function (event) { jsonMsg=event.data; var json = JSON.parse(jsonMsg); var msg=json["jsonMessage"]; if (window[msg]) { window[msg](); //It is

My first JSF page was throwing javax.faces.application.ViewExpiredException . while I searched I got this solution which solved my problem. <context-param> <param-name>javax.faces.STATE_SAVING_METHOD</param-name> <param-value>client</param-value> </context-param> But I am concerned about the security implication. BalusC This doesn't save the "session" in client side at all. This only saves the JSF view state in client side. This is in JSF 2.2 always AES-encrypted with a key which is generated on application startup. This however invalidates once you restart the application, hereby causing all

I'm using an <h:outputLink> as follows. <c:set var="cid" value="1"/> <c:set var="sid" value="2"/> <h:outputLink value="Test.jsf"> <h:outputText value="Link"/> <f:param name="cid" value="#{cid}"/> <f:param name="sid" value="#{sid}"/> </h:outputLink> This is just an example. Both of the query-string parameters are dynamic. So, <c:set> used here is just for the sake of demonstration. At any time, either one, both or none of the parameters may be present. In case, if only one or none of them is present then, parameter/s are unnecessarily appended to the URL which should not happen. Preventing

I'm executing the following jQuery function on <p:dataTable> filter (whose id is id ) that allows users to enter only digits in the filter component. $(document).ready(function() { $("#form\\:dataTable\\:id\\:filter").keydown(function(event) { //Allow: tab, escape, and enter if(event.keyCode===9||event.keyCode===27||event.keyCode===13|| //Allow: Ctrl+A, Ctrl+C (event.keyCode===65&&event.ctrlKey===true)||(event.keyCode===67&&event.ctrlKey===true)|| //Allow: home, end, left, right (event.keyCode>=35&&event.keyCode<=39)){ //let it happen, don't do anything event.preventCapture(); return; }/