jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "angela (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (JCR-181) jcr-server should honor a webdav request's Content-Type and Content-Language headers
Date Fri, 19 Aug 2005 14:24:54 GMT
     [ http://issues.apache.org/jira/browse/JCR-181?page=all ]
     
angela resolved JCR-181:
------------------------

    Resolution: Fixed

------------------------------------------------------------------------------------------------
1) Content-Language
------------------------------------------------------------------------------------------------
- header value is set if present (retrieved from the dav resource)
- simple DavResourceImpl inits the content-langage dav property if it 
   is available from the resouce.
- extended export/importcontext so they honour content-language  prop.

------------------------------------------------------------------------------------------------
2) ContentType/ContentLanguage when adding member resources
------------------------------------------------------------------------------------------------
modified the davresource in order to allow to pass a context rather than only an input stream
to the addMember method. the context current provides contentype/contentlanguage/inputstream.

regards
angela

> jcr-server should honor a webdav request's Content-Type and Content-Language headers
> ------------------------------------------------------------------------------------
>
>          Key: JCR-181
>          URL: http://issues.apache.org/jira/browse/JCR-181
>      Project: Jackrabbit
>         Type: Bug
>     Reporter: Brian Moseley
>     Assignee: angela

>
> when processing a PUT or a POST, the DavResource should have access to the Content-Type
and Content-Language headers presented in the webdav request, if any.
> when the client explicitly communicates these headers, their values should take priority
over server calculations (such as that done in SetContentTypeCommand), or at least be input
into server calculations
> furthermore, the dav getcontentlanguage is not at all supported by at least the simple
webdav server.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message