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
New Component APIs to manage EL context as it applies to components. #1080
Comments
@glassfishrobot Commented |
@glassfishrobot Commented |
@glassfishrobot Commented |
@glassfishrobot Commented |
@glassfishrobot Commented Sending jsf-api/src/main/java/javax/faces/component/UIComponent.java A better use of my time is to try to implement the API that Blake mentioned from Trinidad ComponentContextManager. Ed |
@glassfishrobot Commented The latest commit for this issue broke the trunk build. When can we expect a resolution on this? Manfred |
@glassfishrobot Commented Seems to be blue, and it's from r9772. Is also blue, and that's from r9769. Can you please point me to the failing job? I'll fix it right away, of course. |
@glassfishrobot Commented |
@glassfishrobot Commented |
@glassfishrobot Commented |
@glassfishrobot Commented |
|
B> The issue with clientIds is that portions of the clientId are an
B> implementation detail of the components and renderkit. The result is
B> that developers are not supposed to be hardcoding clientIds into their
B> code. Developers need a different kind of id that specifies context
B> like a clientId, but is standardized like a findComponent search
B> expression. Let's call this a contextId.
B> Given a contextId, we would like to be able to do the following:
B> 1) Efficiently convert the contextId into an object capable of
B> establishing and tearing down the context for the component relatively
B> efficiently. This would require new component apis.
B> 2) Add a function like findComponentInContext that may return a proxy
B> for the UIComponent executing in the context object from 1)
B> 3) Since setting up and tearing down context on every attribute
B> retrieval is inefficient--framework managed context so that the current
B> context may be torn down lazily.
Affected Versions
[1.1, 1.2, 2.0, 2.1]
The text was updated successfully, but these errors were encountered: