You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@myfaces.apache.org by Keith Carlton <ke...@familyvideo.com> on 2010/04/07 18:54:06 UTC
RE: [TRINIDAD] Family and component type for
SelectRangeChoiceRenderer
Carsten,
I am working on a similar problem, can you please post your xml addition to
the faces-config.xml
that get the renderer to see you renderKit?
Thanks,
Keith
Carsten Pieper wrote:
>
> If anyone is interested, here's the solution to the problem.
>
> I did exactly what Harald advised (writing our own TableRenderer whose
> inner private class
> NavBar extends MySelectRangeChoiceRenderer).
>
> But as TableRenderer is an abstract class I also had to write our own
> version of the
> DesktopTableRenderer which now extends our TableRenderer. In our
> CoreRenderKit's
> constructor the only thing I had to add is this
>
> addRenderer("org.apache.myfaces.trinidad.Table",
> "org.apache.myfaces.trinidad.Table", new DesktopTableRenderer());
>
> Note that there's no need to add a renderer for our
> SelectRangeChoiceRenderer (i.e.
> MySelectRangeChoiceRenderer). The reason for this most probably is, that
> it's not a
> real component but more of a sub-component of the table...
>
> Cheers, Carsten
>
>
> Carsten Pieper wrote:
>>
>> Harald wrote:
>>> I.e. the renderer
>>> org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.TableRenderer
>>> has a
>>> static private class NavBar extends SelectRangeChoiceBarRenderer
>> That's a very good hint. So probably I'm just writing our own
>> TableRenderer and put our stuff
>> directly into the private NavBar class.
>>
>>
>>
>>
>
>
--
View this message in context: http://old.nabble.com/-TRINIDAD--Family-and-component-type-for-SelectRangeChoiceRenderer-tp26498105p28167772.html
Sent from the MyFaces - Users mailing list archive at Nabble.com.
RE: [TRINIDAD] Family and component type for
SelectRangeChoiceRenderer
Posted by Carsten Pieper <ca...@continentale.de>.
Hi Keith,
I hope I got your question right. This is the render-kit entry from our
faces-config.xml
<render-kit>
<render-kit-id>de.continentale.vu.jsf.base.core</render-kit-id>
<render-kit-class>de.continentale.vu.jsf.base.renderkit.core.ExtendedCoreRenderKit</render-kit-class>
</render-kit>
where ExtendedCoreRenderKit extends
org.apache.myfaces.trinidadinternal.renderkit.core.CoreRenderKit...
Please note that I didn't have to change the faces-config.xml to solve this
problem.
The render-kit entry has already been in and no new entries whatsoever had
to be added.
Hope this helps, Carsten
Keith Carlton wrote:
>
> Keith wrote:
>
> Carsten,
>
> I am working on a similar problem, can you please post your xml addition
> to the faces-config.xml
> that get the renderer to see you renderKit?
>
> Thanks,
>
> Keith
>
>
> Carsten Pieper wrote:
>>
>> If anyone is interested, here's the solution to the problem.
>>
>> I did exactly what Harald advised (writing our own TableRenderer whose
>> inner private class
>> NavBar extends MySelectRangeChoiceRenderer).
>>
>> But as TableRenderer is an abstract class I also had to write our own
>> version of the
>> DesktopTableRenderer which now extends our TableRenderer. In our
>> CoreRenderKit's
>> constructor the only thing I had to add is this
>>
>> addRenderer("org.apache.myfaces.trinidad.Table",
>> "org.apache.myfaces.trinidad.Table", new DesktopTableRenderer());
>>
>> Note that there's no need to add a renderer for our
>> SelectRangeChoiceRenderer (i.e.
>> MySelectRangeChoiceRenderer). The reason for this most probably is, that
>> it's not a
>> real component but more of a sub-component of the table...
>>
>> Cheers, Carsten
>>
>>
>
--
View this message in context: http://old.nabble.com/-TRINIDAD--Family-and-component-type-for-SelectRangeChoiceRenderer-tp26498105p28175486.html
Sent from the MyFaces - Users mailing list archive at Nabble.com.