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-16 20:56 ------- This are nearly my thoughts. The only problem I see is that the @mime-type of a serializer component declaration comes out of the serializer selector (o.a.c.treeprocessor.sitemap.ComponentsSelector.getMimeTypeForHint(Object hint)), while the encoding is set in the configuration of the serializer component declaration. The serializers subclassing AbstractTextSerializer do not even know their mime type because of the above mentioned selection. Where do you want to bring this information together when the serializer does not have information about mime type and the pipeline does not have information about encoding?
