-
Notifications
You must be signed in to change notification settings - Fork 112
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
All inputs inside composite component executed when using <f:ajax> execute="@this" #5032
Comments
codylerum
changed the title
All inputs inside composite component executed when using f:ajax execute="@this"
All inputs inside composite component executed when using <f:ajax> execute="@this"
Jan 7, 2022
Point taken. This should indeed not happen. |
While implementing the IT, I noticed that a work around is to simply omit the |
BalusC
added a commit
that referenced
this issue
Jan 13, 2022
Implement integration test for issue 5032
BalusC
added a commit
that referenced
this issue
Jan 13, 2022
Fix case when f:ajax is handled by cc:insertChildren
Merged
@BalusC Thanks for the quick response. If anyone else runs in to this you can also just directly reference the client id that would be the correct
|
BalusC
added a commit
that referenced
this issue
Jan 13, 2022
Merge remote-tracking branch 'origin/2.3' into 3.0
All merged now. |
FYI impl has been further improved in #5294 |
BalusC
added a commit
that referenced
this issue
Sep 7, 2023
BalusC
added a commit
that referenced
this issue
Sep 7, 2023
…adoc_errors Fix javadoc errors on #5032 (com.sun.faces.* is also checked in 4.0)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
After upgrading from Wildfly 24 to Wildfly 26 have run into a regression in mojarra. This was an upgrade from mojarra 2.3.14 to 2.3.17
What is happening is that I'm using a simple composite component as a layout.
This has worked fine up until now. However now I am seeing that if I have a <f:ajax anywhere within the inserted children then an execute value of
@this
means the entire contents of the composite component. For exampleWhen a value is selected in the
selectOneMenu
it executes bothcompositejob
andcompositeFirstName
which may cause things to fail ifcompositeFirstName
is required=true and unset.I've prepared a repo project at https://github.com/codylerum/execute-this which shows the issue. If you deploy this on Wildfly 24 both pages will work and if you deploy it on Wildfly 26 then the composite version will fail.
I'm assuming this is a result of #4915
@BalusC is what I'm seeing the expected behavior, or should it only apply to all the contents of the composite if the
f:ajax
is a direct child of the composite, likeThe text was updated successfully, but these errors were encountered: