You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Jon Harley (JIRA)" <de...@myfaces.apache.org> on 2006/05/10 19:03:46 UTC
[jira] Commented: (TOMAHAWK-78) Error-page problem with
ExtensionsFilter
[ http://issues.apache.org/jira/browse/TOMAHAWK-78?page=comments#action_12378950 ]
Jon Harley commented on TOMAHAWK-78:
------------------------------------
I had this same problem when using MyFaces 1.1.1, but it has gone away with MyFaces core 1.1.3 + Tomahawk 1.1.2
Looks like the issue is fixed.
> 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
Re: [jira] Commented: (TOMAHAWK-78) Error-page problem with
ExtensionsFi
Posted by Freya <Fr...@howest.be>.
I have the same problem with MyFaces1.1.3 and Tomahawk1.1.2, could there be
any other problem?
(JSF version?)
--
View this message in context: http://www.nabble.com/-jira--Created%3A-%28MYFACES-1096%29-Error-page-problem-with-ExtensionsFilter-t1074854.html#a5053804
Sent from the My Faces - Dev forum at Nabble.com.