[
https://issues.apache.org/jira/browse/TAPESTRY-607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12472629
]
Risto Reinpõld commented on TAPESTRY-607:
-----------------------------------------
I agree with Curtis Paris. This workaround avoids calling 'setContentType'
multiple times, but this really does not help, because 'reset' is called
multiple times. That is why no content-type header is sent at all with response.
One way to overcome this issue, is by calling 'resetBuffer' instead of 'reset'.
This leaves the initial content-type intact. If the content-type of your error
page is different, then there is probably no other way than fix tomcat.
> Output encoding problem with some versions of Tomcat 5
> ------------------------------------------------------
>
> Key: TAPESTRY-607
> URL: https://issues.apache.org/jira/browse/TAPESTRY-607
> Project: Tapestry
> Issue Type: Bug
> Components: Framework
> Affects Versions: 4.0
> Environment: jdk1.4,tapestry4-beta5
> Reporter: Jone
> Assigned To: Howard M. Lewis Ship
> Fix For: 4.0
>
> Attachments: tapestry-607.zip
>
>
> After upgrading my project from beta4 to beta5,the utf-8 encoded
> Chinses,Japanese characters comes into "????".In fact ,the problem occurs in
> continuous actived pages.For example,In page1,in direct lisener mehtod
> invoke "cycle.active('page2')",then in page2,in pageBeginRender() invoke
> "cycle.active(page3)",now in rendered page3,all the "utf-8" character comes
> in to "????".
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
