AFAIK, UIComponent.findComponent(String) receives a "scoped" id rather than a client id, since it just traverses the component hierarchy, rather than factoring in any "current row" for cases such as UIData.
So, although the exact structure of client id is privately controlled by the Renderer as an implementation detail, the syntax of the scoped id passed to findComponent is well-defined. In certain cases, the a component's client id and scoped id may happen to have the same value, but that does not imply that client id is supposed to work with findComponent in all cases.
Kind Regards,
John Fallows.
On 1/23/06, Martin Marinschek <[EMAIL PROTECTED]> wrote:
Hi guys,
I'm opening a can of worms here - I just discussed with John for quite
some time, and now there is a new point that represents a problem to
me.
So a short question to the spec-gurus - how are findComponent and
Renderer.convertClientId supposed to work together?
findComponent makes assumptions on the structure of a passed clientId,
convertClientId has no restrictions whatsoever (as for the spec) on
what it is allowed to do with the client-id. Doesn't that represent a
problem?
regards,
Martin
--
http://www.irian.at
Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German
Professional Support for Apache MyFaces
--
http://apress.com/book/bookDisplay.html?bID=10044
Author: Pro JSF and Ajax: Building Rich Internet Components, Apress
