> i can't get my jsf component to work within a facelets 
> environment. I took the example of Bruno Aranda, a kind of 
> hello world example 
> (http://brunoaranda.googlepages.com/jsfcomponentsarchetype2).
> 
> This works for me with jsps. When i switch to facelets, i get 
> the following warnings and nothing of my component is rendered:
> 
> 16.05.2008 16:38:58 
> org.apache.myfaces.renderkit.html.HtmlRenderKitImpl
> getRenderer
> WARNUNG: Unsupported component-family/renderer-type:

You need more than just the facelet-taglib support.  There's integral
stuff that has to go into the code before it's usable.

This message indicates that you are not returning a valid component
and/or renderer type from the component body tag.  The values returned
from the getRendererType() and getComponentType() methods are used as
lookups against the faces-config.xml and taglib.xml files in the
component jar file.

Bruno's article talks about both of the files and what needs to go into
them, but it looks like you're still missing some pieces...

Personally I didn't use archetype for our JSF/Facelets components.  They
are really simple to hand-code, and (outside of standard method
overrides) there's not a whole lot of boilerplate code that I can see
archetype saving you much time on.

And I still can't get away from the belief that w/o hand coding things
like this you'll never make heads or tails out of code generated by a
tool on your behalf...

Reply via email to