[
https://issues.apache.org/jira/browse/MYFACES-4040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17645976#comment-17645976
]
Werner Punz commented on MYFACES-4040:
--------------------------------------
I have rolled the fix into 2.3-Next and 4.0, I also will roll the ab changes
into the pull request.
The question remains open, to especially [~paulnicolucci] whether we are going
to roll it back intop 2.3, this will be a bigger change on the java codebase
than in the other branches, given it has not the Ajax renderer in.
Since we have synched the rest of the codebase already in the javascript area,
I would be in favor for a backport.
> <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
> Assignee: Werner Punz
> Priority: Major
> Attachments: test-faces23-ajax.war
>
>
> 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
(v8.20.10#820010)
