Re: extending tree2

[Sean Schofield <se...@gmail.com>]

Interesting.  You are saying that the renderer needs to be overridden
along with the component if you decide to override the component. 
That's sounds possible but I can't say why that would be necessary.  I
will check with some of the devlopers and see if this is intentional
or a known limitation.

sean


On Mar 31, 2005 11:43 AM, Rob Decker <ro...@objectsource.org> wrote:
> I don't know why, but if I didn't add the renderer element to my app's faces-
> config.xml I got an empty page. I didn't have to extend HtmlRenderer, I just had to
> add the element to my app's faces-config.xml. I remember reading somewhere about the
> faces-config.xml inheritance model and it said it looks in the jar first, then your
> app's, which can override what is in the jar. But apparently you can't just override a
> component without overriding the renderer too (unless it's bug).
> 
> My tree component works though.
> 
> --
> Rob
> 
> @objectsource.org
> 
> ---------- Original Message -----------
> From: Sean Schofield <se...@gmail.com>
> To: MyFaces Discussion <my...@incubator.apache.org>
> Sent: Thu, 31 Mar 2005 11:33:39 -0500
> Subject: Re: extending tree2
> 
> > > Although the renderer descriptor is verbatim from the myfaces faces-config.xml
> when I
> > > didn't have it in my app's faces-config.xml nothing was rendered.
> >
> > Huh?  If you did not specify your own renderer, etc. in *your*
> > faces-config.xml then you should still have been able to render your
> > tree using the tree2 and renderer that ships with myfaces.  If not
> > then there was likely some other problem going on.
> >
> > So were you successful in providing your own tree component once you
> > got this squared away?
> >
> > > Rob
> >
> > sean
> ------- End of Original Message -------
> 
>