That's verified? It's what webben has been working on, right? According to the servlet API contract setResponseType should work, and setCharsetEncoding just overrides the response type's encoding...
Anyway, I'm fine with upgrading anyway; 2.4 is a couple years old now, isn't it? I think it's pretty much the standard. But maybe some users have different ideas on this. Eelcoo On 5/30/06, Johan Compagner <[EMAIL PROTECTED]> wrote:
Some have problems because a container doesn't set the right header responses when response.setCharsetEncoding() is not called But that is a 2.4 method not a 2.3. Can we upgrade to 2.4? Which version is that for the most used ServletContainers? jjohan
------------------------------------------------------- All the advantages of Linux Managed Hosting--Without the Cost and Risk! Fully trained technicians. The highest number of Red Hat certifications in the hosting industry. Fanatical Support. Click to learn more http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642 _______________________________________________ Wicket-develop mailing list Wicket-develop@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-develop
