Torsten Dettborn wrote:
> > For the time being, I have hacked around this in the 286-COMPATBILITY
> > branch. Do you want the fix, or should we just ignore it until the
> > 286-MERGER branch is further along?
> this is a small patch, isn't it? When you can wait, I would be happy,
> to patch it after merging.
It is a small patch, but currently *too* small a patch. I hacked around the
problem last night with two lines of code, but I need to change it to
properly handle the semantic of returning null when getContentType() is
called unless the user explicitly calls setContentType(). Internally, we
need a default content type to use when getContentType() returns null.
--- Noel
