myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Werner Punz (JIRA)" <...@myfaces.apache.org>
Subject [jira] [Resolved] (MYFACES-3222) jsf.js: jsf.ajax.request params parameter not processed
Date Thu, 14 Jul 2011 12:16:59 GMT

     [ https://issues.apache.org/jira/browse/MYFACES-3222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Werner Punz resolved MYFACES-3222.
----------------------------------

    Resolution: Invalid

> 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

        

Mime
View raw message