Skip to content
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

UIData#invokeOnComponent shouldn't proceed if the clientId doesn't start with the UIData clientId #4262

Closed
ren-zhijun-oracle opened this issue Jul 13, 2017 · 10 comments
Assignees
Labels
Milestone

Comments

@ren-zhijun-oracle
Copy link
Contributor

The new Search Expressions uses findComponent or invokeOnComponent (as fallback) to get a component by id.

I have a case, where the "value" attribute of the dataTable is not yet completely resolveable and it not yet rendered.

If i use invokeOnComponent to search a component, which is placed outside of the datatable, and it hits the datatable, the dataTable will throw a exception because of the unresolvable EL.
The best way to fix this would be if UIData#invokeOnComponent would check if the clientIdToSearch starts with the UIData clientId.
If it doesn't match, invokeOnComponent in the UIData can be completely skipped.

It's already implemented that way in MyFaces: http://grepcode.com/file/repo1.maven.org/maven2/org.apache.myfaces.core/myfaces-api/2.1.9/javax/faces/component/UIData.java#359

This is likely also a great performance improvement for some cases.

@ren-zhijun-oracle
Copy link
Contributor Author

@edburns Commented
Please see this important message regarding community contributions to
Mojarra.

https://javaee.groups.io/g/jsf-spec/message/30

Also, please consider joining that group, as that group has taken the
place of the old [email protected] mailing list.

Thanks,

Ed Burns

@ren-zhijun-oracle
Copy link
Contributor Author

@larslorenzen
Copy link

Please fix this, it prevents us from migrating to java ee 8 because EL expressions in a datatable are executed even when the table itself is not rendered.

At least the scope of the try/finally (this.setRowIndex(savedRowIndex);) in the invokeOnComponent method should be greatly reduced to only cover the part where the index is set.

@github-actions
Copy link

This issue is marked as stale because there was no activity on it for the last 2 years. Remove stale label or comment or this will be closed in 30 days

@github-actions github-actions bot added the Stale label Aug 29, 2021
@tandraschko
Copy link
Contributor

Still not fixed

@github-actions github-actions bot removed the Stale label Aug 30, 2021
@mnriem mnriem added the 3.0 label Nov 27, 2021
@mnriem
Copy link
Contributor

mnriem commented Feb 28, 2022

@tandraschko Can you supply a reproducer and/or fix?

@tandraschko
Copy link
Contributor

it could be that it was fixed with this https://github.com/eclipse-ee4j/mojarra/pull/4506/files but i didnt verify it

@BalusC
Copy link
Contributor

BalusC commented Sep 9, 2023

If i use invokeOnComponent to search a component, which is placed outside of the datatable, and it hits the datatable, the dataTable will throw a exception because of the unresolvable EL.

A reproducer is welcome. I'm having difficulty understanding the issue.

@BalusC
Copy link
Contributor

BalusC commented Sep 16, 2024

Closing off as stale.

@BalusC BalusC closed this as completed Sep 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

6 participants