[
http://issues.apache.org/jira/browse/MYFACES-1096?page=comments#action_12366216
]
Alexander Golubev commented on MYFACES-1096:
--------------------------------------------
I try out all casses but without success. if you look at the code of
ExtensionsFilter ...
// here we call next filter
chain.doFilter(extendedRequest, extendedResponse);
extendedResponse.finishResponse();
if( ! AddResource.hasAdditionalHeaderInfoToRender(extendedRequest) ){
response.getOutputStream().write( extendedResponse.getBytes());
return;
}
// Some headerInfo has to be added
--> // here we add some header info even if there was an error (404) and
there is no content
AddResource.writeWithFullHeader(extendedRequest, extendedResponse,
(HttpServletResponse)response);
> 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
