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-17 01:46 ------- > is there a use case for such an override? At least in theory, it's the same as for readers. For example for XUL we declared a second XML serializer just with another mime-type. Don't know if we could have declared it on the pipeline (it was 2.0.4), at least we would not need a second declaration. > coming back to responsibilities... it's the processor's responsibility to set > the media type on the Environment (which it gets from the SitemapOutputComponent > or an override). But which one to take? Old 1. and 3. are now tied together, 2. stays in the processor as it is now. If the old 2. is now the prefered way over the getMimeType() of the serializer handling old 1. and 3., it's no longer possible to hardcode the mimetype in the serializer - which might be ok, but it's at least incompatible to current handling.
