myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexander Jesse (JIRA)" <incubator-...@incubator.apache.org>
Subject [jira] Created: (MYFACES-133) Configured but inexistent Renderer is not reported
Date Tue, 15 Mar 2005 14:50:37 GMT
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:
<render-kit>
 <renderer>
  <component-family>javax.faces.Input</component-family>
  <renderer-type>javax.faces.Text</renderer-type>
  <renderer-class>com.jsf.components.renderer.NotExistingRenderer</renderer-class>
 </renderer>
</render-kit>
)


-- 
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
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


Mime
View raw message