DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=26997>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=26997 Encoding in HTTP-Header is not set by Serializer ------- Additional Comments From [EMAIL PROTECTED] 2004-03-18 18:51 ------- The patch moves the handling of the @mime-type on component declaration in the sitemap from ProcessingPipeline to the serializers and readers (though it contains no changes on any reader at the moment). Furthermore now the pipeline is asked first for @mime-type and if there is no value set the reader/serializer is asked. This is a bit different than now as you can read above (and so an incompatibility in behaviour though not in code), hardcoding the mimetype by the serializer is no longer possible. Please review this patch and give your comment. After this change the fix for the content type can be implemented.
