I don't object but I'm curious about how the RI handles this. Doesn't
the RI use ':' with naming containers? If you have a component with
id = 'bar' inside a form with id 'bar' you get 'foo:bar' right? Isn't
that how things always worked?
sean
On 7/1/05, Grant Smith <[EMAIL PROTECTED]> wrote:
> Grant Smith wrote:
>
> > Sean,
> >
> > I just committed a change to InputSuggestRenderer which MAY solve your
> > problem. If it doesn't, it means that the id is being prepended to by
> > something I don't understand. As it is, I don't see how colons are
> > being generated by UIViewRoot.createUniqueId(), so this might just be
> > a klundge until I understand things better.
> >
> > Let me know if it works
>
> OK,
>
> Here is what I now know:
>
> UIComponentBase uses NamingContainer.SEPARATOR_CHAR to build the id. I
> would like to propose changing
>
> public interface NamingContainer
> {
> public static final char SEPARATOR_CHAR = ':';
> }
>
> to
>
> public interface NamingContainer
> {
> public static final char SEPARATOR_CHAR = '_';
> }
>
> and removing all the
>
> component.getClientId(context).replaceAll(":","_")
>
> constructs scattered throughout the system. Any objections ?
>
>
>
