Incidently, the fact that tomcat seems to remove any space between the ; and charset in "mimetype; charset=..." whereas apache seems to prefer to add one is an annoying inconsistency that has blocked a much simpler workaround for my difficulties (one that would have used text/xml).
No matter. My next step is to link in the velocity engine. Funnily enough, this requires a Writer object, whereas I now have a ServletOutputStream. I guess I will have to use the constructor in java.io.OutputStreamWriter since I cannot use the more direct getWriter() method! Ironic isn't it? Apart from the fact I have to specify the charset carefully, can you foresee any possible problems? Thanks for all the help, it's very much appreciated. Richard > Richard Kaye wrote: >> Thank you! I was using a writer and switching to a >> ServletOutputStream fixed it. I never thought of that: >> the specs say streams are intended for binary data... > > They do. They also say if you use a writer Tomcat must append a > charset to the Content-Type header. > > Glad this works now. > > Mark > > --------------------------------------------------------------------- > To start a new topic, e-mail: users@tomcat.apache.org > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
