[jira] Commented: (MYFACES-1096) Error-page problem with ExtensionsFilter

["Sukhada (JIRA)" <de...@myfaces.apache.org>]

    [ http://issues.apache.org/jira/browse/MYFACES-1096?page=comments#action_12365774 ] 

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

In your web.xml try changing your url-pattern. Because I was having the same problem but I fixed changing the url-patterns.

For e.g. 

for eclipse it worked with this code 

<filter>
    <filter-name>MyFacesExtensionsFilter</filter-name>
    <filter-class>org.apache.myfaces.component.html.util.ExtensionsFilter</filter-class>
  </filter>
  <filter-mapping>
    <filter-name>MyFacesExtensionsFilter</filter-name>
    <url-pattern>*.faces</url-pattern>
  </filter-mapping>
  <filter-mapping>
    <filter-name>MyFacesExtensionsFilter</filter-name>
    <url-pattern>/faces/*</url-pattern>
  </filter-mapping>


and for jbuilder I have different mapping.

<filter>
    <filter-name>MyFacesExtensionsFilter</filter-name>
    <filter-class>org.apache.myfaces.component.html.util.ExtensionsFilter</filter-class>
  </filter>
  <filter-mapping>
    <filter-name>MyFacesExtensionsFilter</filter-name>
    <url-pattern>*.faces</url-pattern>
  </filter-mapping>
  <filter-mapping>
    <filter-name>MyFacesExtensionsFilter</filter-name>
    <url-pattern>/faces/*</url-pattern>
  </filter-mapping>

If you your jsp page is under 'foo' folder then try url-pattern like 

<url-pattern>/foo/*</url-pattern>


Hope this will help.

Sukhada.



> 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