Return-Path: Delivered-To: apmail-myfaces-dev-archive@www.apache.org Received: (qmail 85903 invoked from network); 26 May 2005 06:52:10 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 26 May 2005 06:52:10 -0000 Received: (qmail 90208 invoked by uid 500); 26 May 2005 06:52:08 -0000 Delivered-To: apmail-myfaces-dev-archive@myfaces.apache.org Received: (qmail 90170 invoked by uid 500); 26 May 2005 06:52:08 -0000 Mailing-List: contact dev-help@myfaces.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "MyFaces Development" Delivered-To: mailing list dev@myfaces.apache.org Received: (qmail 89928 invoked by uid 99); 26 May 2005 06:52:08 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from ajax-1.apache.org (HELO ajax.apache.org) (192.87.106.226) by apache.org (qpsmtpd/0.28) with ESMTP; Wed, 25 May 2005 23:52:06 -0700 Received: from ajax.apache.org (ajax.apache.org [127.0.0.1]) by ajax.apache.org (Postfix) with ESMTP id 9966C194 for ; Thu, 26 May 2005 08:52:00 +0200 (CEST) Message-ID: <20585346.1117090320626.JavaMail.jira@ajax.apache.org> Date: Thu, 26 May 2005 08:52:00 +0200 (CEST) From: "Martin Marinschek (JIRA)" To: dev@myfaces.apache.org Subject: [jira] Commented: (MYFACES-133) Configured but inexistent Renderer is not reported Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N [ http://issues.apache.org/jira/browse/MYFACES-133?page=comments#action_66332 ] Martin Marinschek commented on MYFACES-133: ------------------------------------------- This is the corresponding source-code: javax.faces.render.Renderer renderer = null; try { renderer = (javax.faces.render.Renderer) ClassUtils.newInstance(element.getRendererClass()); } catch(FacesException e) { // ignore the failure so that the render kit is configured log.error("failed to configure class " + element.getRendererClass(), e); continue; } I would suppose that the logging should be exactly what you refer to, I don't know why this would still not be logged? regards, Martin > Configured but inexistent Renderer is not reported > -------------------------------------------------- > > Key: MYFACES-133 > URL: http://issues.apache.org/jira/browse/MYFACES-133 > Project: MyFaces > Type: Bug > Versions: 1.0.8 beta > Environment: Tomcat 5.0.28 > Reporter: Alexander Jesse > Priority: Minor > Attachments: MinimalMyFaces.zip, MinimalRI.zip, TomcatConfig_Log.zip > > A configured but inexistent renderer is not reported and the myfaces-application starts using the supplied standard renderer. The SUN-RI reports a "java.lang.ClassNotFoundException: com.jsf.components.renderer.NotExistingRenderer" which helps to pinpoint the configuration error. > For production this can be a desired behaviour but presents some danger at the same time. Not having the information at hand I wondered why my renderer would not decorate the input-field as planned. When I tried the same renderer in the RI the error (wrong classname) was found in 30 seconds. > The error is easy to reproduce: > Take an existing JSF-application and add a phantom renderer to the faces-config.xml. Then start the web-container. > (sample config-entry: > > > javax.faces.Input > javax.faces.Text > com.jsf.components.renderer.NotExistingRenderer > > > ) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira