[
https://issues.apache.org/jira/browse/MYFACES-4040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17644130#comment-17644130
]
Volodymyr Siedlecki commented on MYFACES-4040:
----------------------------------------------
Bringing attention to this since it's part of the Faces TCK:
Mojarra Issue: https://github.com/eclipse-ee4j/mojarra/issues/4119
App:
https://github.com/jakartaee/faces/blob/4.0.1/tck/faces23/ajax/src/main/webapp/issue4115.xhtml
Test:
https://github.com/jakartaee/faces/blob/4.0.1/tck/faces23/ajax/src/test/java/ee/jakarta/tck/faces/test/javaee8/ajax/Issue4115IT.java#L82
Leo's reply in the thread above can be found here:
https://download.oracle.com/javaee-archive/javaserverfaces-spec-public.java.net/jsr372-experts/2016/03/0984.html
I don't fully understand why this not a bug, but I'm hoping may [~werpu] or
[~tandraschko] might be able to comment here some, if either of you have time?
Why shouldn't f:param not sent the execute=bar as part of the request?
Although, this is a niche behavior, and we could create a challenge?
> <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: Leonardo Uribe
> Priority: Major
>
> 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)
