You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Leonardo Uribe (JIRA)" <de...@myfaces.apache.org> on 2016/04/26 06:23:13 UTC
[jira] [Commented] (MYFACES-4040) name conflicts with
attributes
[ https://issues.apache.org/jira/browse/MYFACES-4040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15257543#comment-15257543 ]
Leonardo Uribe commented on MYFACES-4040:
-----------------------------------------
Discussed in:
[jsr372-experts mirror] [jsr372-experts] jsf.ajax.request() options.params is never considered in Mojarra
https://java.net/projects/javaserverfaces-spec-public/lists/users/archive/2016-03/message/19
Something was fixed on Mojarra but our code is fine. Closing issue as not a bug.
> <f:param> name conflicts with <f:ajax> attributes
> -------------------------------------------------
>
> Key: MYFACES-4040
> URL: https://issues.apache.org/jira/browse/MYFACES-4040
> Project: MyFaces Core
> Issue Type: Bug
> Components: General
> Affects Versions: 2.2.9
> Reporter: Bauke Scholtz
>
> https://java.net/jira/browse/JAVASERVERFACES-4115 also applies to MyFaces.
> {code}
> <h:form>
> <h:inputText id="foo" />
> <h:commandLink value="test">
> <f:ajax execute="foo" />
> <f:param name="execute" value="bar" />
> </h:commandLink>
> </h:form>
> {code}
> In MyFaces, the actual behavior is equal to <f:ajax execute="bar"> and request.getParameter("execute") returns null.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)