On 25.05.2004 12:00, Carsten Ziegeler wrote:
http://issues.apache.org/bugzilla/show_bug.cgi?id=26997
One of them is the order in which the mime-type is evaluated. I think we should change if for the serializer as well in order to make it equal to the order used for the reader. So the order should be: - optional configured mime-type in the usage of the serializer (perhaps this can be removed) - configured mime-type in the configuration of the serializer - ask the serializer
Yes, for consistency.
Now for the encoding. In general I would say that a serializer is configured with a mime-type and (perhaps) with an encoding. Now, a working solution should be that the serializer is configured with the combination of mime-type and encoding: <map:serializer mime-type="MT;ENCODING".../> This should work out of the box. It has only the disadvantage that you configure the encoding twice on the serializer.
WDYT?
To be honest I really don't like it. Why shall a user have to care what comes out at the end (the header) and why he has to know the needed format for it ("mimetype;charset")? To say nothing of the duplicate configuration and the nice effects if you change one and forget the other one ... IMO the serializer must know the encoding in any case, so it should get the complete control over it and the pipeline (setting the header) only asks the serializer. This is what I tried with the patch.
Joerg
