[
https://issues.apache.org/jira/browse/MYFACES-3222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13065203#comment-13065203
]
Werner Punz commented on MYFACES-3222:
--------------------------------------
Ok after running a blackbox test against the latest mojarra I ran into
following result for an addtional params map
params [object Object]
this is exactly the same behavior we have in myfaces (I probably have run this
test before)
I assume the spec is at fault here.
So I will close this issue.
> jsf.js: jsf.ajax.request params parameter not processed
> -------------------------------------------------------
>
> Key: MYFACES-3222
> URL: https://issues.apache.org/jira/browse/MYFACES-3222
> Project: MyFaces Core
> Issue Type: Bug
> Affects Versions: 2.0.7, 2.1.1
> Environment: javascript
> Reporter: Werner Punz
> Assignee: Werner Punz
>
> The jsf 2.x jsdocs state that params is one option value allowed, which
> allows params to be added to be included in the request.
> Currently we handle that by simply parsing additional options params.
> I have to crosscheck via a black box test if our behavior is also allowed or
> if we have to process the params explicitely as submap.
> I assume params is a submap (the spec is not fully clear) but given that it
> is stated as allowed key it must be like that.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
