Juergen,
Probably something went wrong with your changes. When an error page is generated by Wicket, it gets returned as an 'application/octet-stream' stream, instead of a html file. My browser wouldn't open the html file containing the error page.
Martijn
Juergen Donnerstag wrote:
I'm going to commit the following solution in a couple of minutes and I'll update the wiki encoding page as well.
1) <?xml ..encoding=".." ?> will be used to determine the encoding of the file and be used to properly transfer the markup's encoding into utf-16 which is used by JVM internally
2) The xml declaration string "<?xml ....?>" will not be added to the Markup's list of MarkupElements. Instead the string as well as the encoding will be available through getters of MarkupStream.
3) During Page.configureResponse() the xml declaration string is taken from (the Page's) Markup, if available and is written to the response as the very first data. In addition, if encoding is available, the http header is modified to add the encoding information. Thus header and data encodings are consistent.
Juergen
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Wicket-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Wicket-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop
