You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Esteve (JIRA)" <de...@myfaces.apache.org> on 2006/06/10 18:45:31 UTC
[jira] Commented: (TOMAHAWK-78) Error-page problem with
ExtensionsFilter
[ http://issues.apache.org/jira/browse/TOMAHAWK-78?page=comments#action_12415678 ]
Esteve commented on TOMAHAWK-78:
--------------------------------
Hi all,
I've found that using jsp forwards like "<jsp:forward page="login.faces"/>" this error appears, but if you access directly to the page, passing through faces servlet all works find.
I know it doesn't add much value but it could help somebody. I've spended a pair of hours on this trick....
Bye
> Error-page problem with ExtensionsFilter
> ----------------------------------------
>
> Key: TOMAHAWK-78
> URL: http://issues.apache.org/jira/browse/TOMAHAWK-78
> Project: MyFaces Tomahawk
> Type: Bug
> Components: ExtensionsFilter
> 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