You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by Dreamltf <h9...@gmail.com> on 2008/06/23 08:23:41 UTC

Re: WebResource vs DynamicWebResource character encoding question

Thanks Wicket!

I found the answer in the Wicket 1.3.4 Release Notes

* [WICKET-1704] - ResourceStreamRequestTarget.configure set wrong
ContentLength for non-ascii characters 

now, it works fine at Wicket 1.3.4

Thanks All
-- 
View this message in context: http://www.nabble.com/WebResource-vs-DynamicWebResource-character-encoding-question-tp17998234p18063242.html
Sent from the Wicket - User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org

Re: WebResource vs DynamicWebResource character encoding question

Posted by Dreamltf <h9...@gmail.com>.
Oh no...

I found when I use the StringResourceStream, it works fine

but when I use the StringBufferResourceStream, it still return a wrong
length


Dreamltf wrote:
> 
> Thanks Wicket!
> 
> I found the answer in the Wicket 1.3.4 release notes
> 
> * [WICKET-1704] - ResourceStreamRequestTarget.configure set wrong
> ContentLength for non-ascii characters 
> 
> now, it works fine at Wicket 1.3.4
> 
> Thanks All
> 

-- 
View this message in context: http://www.nabble.com/WebResource-vs-DynamicWebResource-character-encoding-question-tp17998234p18146875.html
Sent from the Wicket - User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org