myfaces-dev mailing list archives

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

Sukhada commented on MYFACES-1096:
----------------------------------

Try taking out "faces" from the url-pattern.

<filter-mapping>
    <filter-name>MyFacesExtensionsFilter</filter-name>
    <url-pattern>/*</url-pattern>
  </filter-mapping>

 If it doesn't work then if your page is under some directory then add that directory's name
and map it.

<filter-mapping>
    <filter-name>MyFacesExtensionsFilter</filter-name>
    <url-pattern>/foo/*</url-pattern>
  </filter-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