It works like a charm, many thanks for the good advice! Regards Henrik 2011/1/17 Rudy De Busscher <[email protected]>
> Hi Henrik, > > You can override the method getRendererType() and return null. Then there > is no search for the renderer done. > > Regards > Rudy. > > > On 17 January 2011 10:36, Henrik Troeng <[email protected]> wrote: > > > Hi, > > I have a large set of custom components for my jsf/facelet/portlet > project. > > I have currently been using SUN-RI implementation, but recently switched > to > > Myfaces 1.2.9. > > > > The components are developed without any specific renderer, the rendering > > is > > done directly under the component (extending the UIComponent family), and > > are specified in faces-config.xml: > > <component> > > <component-type>MY_INPUTTEXT_FAMILY</component-type> > > > > > <component-class>com.mycompany.jsf.component.MyInputTextComponent</component-class> > > </component> > > > > and under my.taglib.xml: > > <tag> > > <tag-name>customInputText</tag-name> > > <component> > > <component-type>MY_INPUTTEXT_FAMILY</component-type> > > </component> > > </tag> > > > > When I switched to the Myfaces implementation WARN messages started to > > appear in the logs. > > > > WARN myfaces.renderkit.html.HtmlRenderKitImpl > > [Unsupported component-family/renderer-type: > > com.mycompany.jsf.component.MyInputTextComponent/javax.faces.Text] > > [2011-01-01 12:43:34:366 CET] 0000003d webapp I > > com.ibm.ws.webcontainer.webapp.WebApp log SRVE0292I: Servlet Message - > > [EARProject#Myportlet.war]:.No Renderer found for component > > {Component-Path : [Class: > > javax.portlet.faces.component.PortletNamingContainerUIViewRoot, > > ViewId: /com/mycompany/facelets/modifyAccount.xhtml] > > [Class: javax.faces.component.html.HtmlForm,Id: updateForm] > > [Class: com.mycompany.jsf.component.MyInputTextComponent,Id: > > updateMobilePhoneNumber]} > > (component-family=MY_INPUTTEXT_FAMILY, renderer-type=javax.faces.Text) > > > > The components still work as expected, but there are a lot of WARN-logs > > being produced now. I have even implemented an empty Renderer and defined > > it > > in faces-config.xml and the messages dissapears then, but it dont feel > > satisfied with having to implement ugly code just to remove logs. > > > > I run the application in Websphere Portal 6.1. > > > > Does anyone know how to get these logs away? > > >
