On Tue, Apr 3, 2012 at 10:30 AM, Edward Burns <edward.burns_at_oracle.com>wrote:
> >>>>> On Mon, 2 Apr 2012 12:15:24 -0400, Kito Mann <kito.mann_at_virtua.com>
> said:
>
> KM> On Mon, Mar 5, 2012 at 9:53 AM, Edward Burns <edward.burns_at_oracle.com
> >wrote:
> >> >>>>> On Mon, 5 Mar 2012 09:31:59 -0500, Kito Mann <
> kito.mann_at_virtua.com>
> >> said:
> >>
> KM> Is there any reason UIComponent.getRenderer() is protected instead of
> KM> public? It'd be nice if it were public, especially when writing test
> KM> code.
>
> EB> Just your garden variety information hiding principles. Does anyone
> EB> else want this? It seems a pity to add a new public method just for
> EB> testing purposes. At this point, we must undertake the addition of new
> EB> API with the greatest care and moderation.
> EB>
>
> KM> Understood, but why does this information need to be hidden?
>
> I would have to do some list forensics to uncover that. Do you think
> it's worth our time to research that?
>
>
No, I don't think so. You can get the renderer by calling
RenderKit.getRenderer(component.getFamily(), component.getRendererType()).
This is just one of those things that seems silly from a development
perspective -- you can manually call getRenderer(), but you can't use the
convenience method that does it for you :-).
> --
> | edward.burns_at_oracle.com | office: +1 407 458 0017
> | homepage: | http://ridingthecrest.com/
>