werpu opened a new pull request, #413:
URL: https://github.com/apache/myfaces/pull/413

   Fix for MYFACES-4040, in my own integration tests:
   
   
   ```xml
              <h:commandLink id="submitButton" value="Click here" 
action="#{myBean2.execute}">
                   <f:ajax execute="@this" render="output" />
                   <f:param name="hello2" value="Hello from f:param"/>
                   <f:param name="Hello World" value="Hello from f:param2"/>
                   <f:param name="render" value="output2"/>
                   <f:param name="execute" value="booga"/>
              </h:commandLink>
   
              <h:panelGroup id="results">
                   <h:outputText id="output" 
value="#{myBean2.helloWorld}"></h:outputText>
              </h:panelGroup>
   ```
   
   Now resolves to:
   
   ```html
   <a href="#" onclick="faces.util.chain(this, 
event,function(event){myfaces.ab(this,event,'action','submitButton','output',{params:
 {'hello2':'Hello from f:param','Hello World':'Hello from 
f:param2','render':'output2','execute':'booga'}})}); return false;" 
id="submitButton" name="submitButton">Click here</a>
   ```
   
   and the test which searches for an updated output element passes, the render 
and execute f:params arw now part of param
   Also the request parameters are now as following:
   
   ```javascript
   form1_SUBMIT: 1
   jakarta.faces.ViewState: ZDU1NmJhYjk2NmVjZDQ5YjAwMDAwMDJk
   hello2:  Hello from f:param
   Hello World: Hello from f:param2
   render: output2
   execute: booga
   jakarta.faces.behavior.event: action
   jakarta.faces.partial.event: click
   jakarta.faces.source: submitButton
   jakarta.faces.partial.ajax: true
   jakarta.faces.partial.execute: submitButton
   jakarta.faces.partial.render: output
   form1: form1
   ```
   @tandraschko @melloware  please test I wont merge the fix until you give the 
ok
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to