You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Vadim Gritsenko <va...@verizon.net> on 2003/11/07 13:48:18 UTC

Syncing with 2.2, Re: DO NOT REPLY [Bug 10277] - Cannot set MIME type for ResourceReader

bugzilla@apache.org wrote:

>Cannot set MIME type for ResourceReader
>  
>
...

>I just changed the impl for 2.2:
>- MIME type declared on the reader instance
>- MIME type declared for the reader component
>- Ask the Reader for a MIME type. A *.doc reader could peek into the file
>  and return either text/plain or application/vnd.msword.
>- MIME type declared in WEB-INF/web.xml or by the server.
>The two last points have to be done by the reader itself, as the reader is the 
>only component knowing the source. So this logic has to be implemented in the 
>reader which I didn't change.
>  
>

Does it make sense to have same in 2.1?

And more general question -- I see some commits flowing into 2.1 branch, 
should those changes be also reflected in 2.2? Or, how else those 
changes will get into 2.2?

Vadim




RE: Syncing with 2.2, Re: DO NOT REPLY [Bug 10277] - Cannot set MIME type for ResourceReader

Posted by Carsten Ziegeler <cz...@s-und-n.de>.
Vadim Gritsenko wrote:
> 
> Does it make sense to have same in 2.1?
> 
We agreed, that these changes should only be in 2.2, but if someone needs
it in 2.1 as well we can add it there, too.

> And more general question -- I see some commits flowing into 2.1 branch, 
> should those changes be also reflected in 2.2? Or, how else those 
> changes will get into 2.2?
> 
We should check in all changes to 2.1 in 2.2 as well - otherwise they
get lost.

Carsten