Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Date: 16 Mar 2004 23:47:19 -0000
Message-ID: <20040316234719.1454.qmail@nagoya.betaversion.org>
From: bugzilla@apache.org
To: dev@cocoon.apache.org
Cc: 
Subject: DO NOT REPLY [Bug 26997]  -
    Encoding in HTTP-Header is not set by Serializer

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 m_rolappe@web.de  2004-03-16 23:47 -------
I think it should be the serializer's (SitemapOutputComponent's) responsibility
to tell the content type, not the serializer selector's one. the handling of the
selector's @mime-type attribute should be delegated to e.g. AbstractSerializer
so that Serializer's which don't know/can't determine their content type
themselves can still be configured with one declared in the sitemap.

the fact that the encoding (which the serializer selector doesn't know about at)
belongs to the content type (or more specifically media type) just hardens the
hint that providing the content/media type is not/cannot be its responsibility.