[ 
https://issues.apache.org/jira/browse/MYFACES-2618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12850929#action_12850929
 ] 

Dave commented on MYFACES-2618:
-------------------------------

This is our use case.

We made an ajax-enabled JSF component. When user changes select value of the 
component, an ajax request with the new select value will be sent to the server 
side.  We use the component decode() method to process the ajax request.

The ajax request parameters:

  var formSubmitParam = select.form.id + "_SUBMIT";   // why need this?
  var url = serverURL + "&ajax=1&sid=" + Math.random() +
    "&" + formSubmitParam + "=1" + 
    "&" + clientId + "=" + selectValue;

the serverURL contains view_state for restoring view. If we do not add the 
formSubmitParam, the component decode() method will not be called.   The url 
above works well for processing ajax request in the decode method. But we got 
the warning. The warning is not prefered. If there is a way to keep it silent, 
it would be great, for example, adding a parameter.




> Don't warn if there is no submitted value in the current request for every 
> EditableValueHolder
> ----------------------------------------------------------------------------------------------
>
>                 Key: MYFACES-2618
>                 URL: https://issues.apache.org/jira/browse/MYFACES-2618
>             Project: MyFaces Core
>          Issue Type: Task
>          Components: JSR-314
>    Affects Versions: 2.0.0-beta-2
>            Reporter: Jakob Korherr
>            Assignee: Jakob Korherr
>            Priority: Minor
>         Attachments: MYFACES-2618.patch
>
>
> Take a look at HtmlRendererUtils.decodeUIInput(): There we do a check for 
> paramMap.containsKey(clientId) and if this returns false (meaning that there 
> is no submitted value for the given component in the request parameter map) 
> we add a warning message to the log.
> I think we should get rid of this warning, because as a reason of AJAX it is 
> on my opinion normal to not submit all values of a form in every request. 
> Furthermore it has no impact on the lifecycle, because if the submitted value 
> is null it just isn't processed any further.
> See also the related thread on the mailing list: 
> http://www.mail-archive.com/us...@myfaces.apache.org/msg55238.html

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to