myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexander Golubev (JIRA)" <...@myfaces.apache.org>
Subject [jira] Commented: (MYFACES-1096) Error-page problem with ExtensionsFilter
Date Mon, 13 Feb 2006 12:19:37 GMT
    [ http://issues.apache.org/jira/browse/MYFACES-1096?page=comments#action_12366191 ] 

Alexander Golubev commented on MYFACES-1096:
--------------------------------------------

I have no  eclipse or jbuilder.
All pages are myfaces pages.
web.xml contains
 <filter>
        <filter-name>ExtensionsFilter</filter-name>
        <filter-class>
            org.apache.myfaces.component.html.util.ExtensionsFilter
        </filter-class>
        <init-param>
            <param-name>uploadMaxFileSize</param-name>
            <param-value>50m</param-value>
        </init-param>
        <init-param>
            <param-name>uploadThresholdSize</param-name>
            <param-value>100k</param-value>
        </init-param>
    </filter>
<filter-mapping>
        <filter-name>ExtensionsFilter</filter-name>
        <url-pattern>*.jsf</url-pattern>        
    </filter-mapping>
<servlet>
        <servlet-name>Faces Servlet</servlet-name>
        <servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
        <load-on-startup>1</load-on-startup>
    </servlet>
    <servlet-mapping>
        <servlet-name>Faces Servlet</servlet-name>
        <url-pattern>*.jsf</url-pattern>
    </servlet-mapping>

> Error-page problem with ExtensionsFilter
> ----------------------------------------
>
>          Key: MYFACES-1096
>          URL: http://issues.apache.org/jira/browse/MYFACES-1096
>      Project: MyFaces
>         Type: Bug
>   Components: Tomahawk
>     Versions: 1.1.1
>  Environment: facelets 1.0.2, tomcat 5.5.12
>     Reporter: Alexander Golubev

>
> It is a problem with getting custom error-page definitions in web.xml
> If I request URL "/blabla.html"
> that doesn't exist, java.lang.IllegalStateException "getOutputStream() has already been
> called for this response" and in the end, the default Tomcat 404 page is
> displayed. 
> The problem is caused by the extensionsfilter that writes header information to the empty
response.

-- 
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


Mime
View raw message