cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 26997] - Encoding in HTTP-Header is not set by Serializer
Date Wed, 17 Mar 2004 00:43:48 GMT
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 joerg.heinicke@gmx.de  2004-03-17 00:43 -------
Good to see my thoughts confirmed: on the one hand for solving this issue, on
the other hand for consistency.

Now the implementation. I might not be the correct person to see all the
consequences, but at least pushing the @mime-type from the component declaration
into the serializer is really easy.

The current order is:
1. ask serializer instance
2. ask serializer in the pipeline's @mime-type handled by treeprocessor
(node/nodebuilder)
3. ask serializer in the component declaration via serializer selector

When the serializer shall handle this completely it is only a question of doing
it with the appropriate lifecycle interfaces I guess (like
AbstractTextSerializer's Configurable).

I only can't see how 2. gets into the serializer except via indirection through
AbstractProcessingPipeline and a call like getMimeType(String
mimeTypeSetInPipeline).

Please cry out when this is nonsense.

WDOT?

Mime
View raw message