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.