You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Claus Köll (JIRA)" <ji...@apache.org> on 2008/02/12 14:39:09 UTC

[jira] Commented: (JCR-1172) Better MimeType Handling

    [ https://issues.apache.org/jira/browse/JCR-1172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12568110#action_12568110 ] 

Claus Köll commented on JCR-1172:
---------------------------------

one more question ...
what is the recommended nodetype for the jcr:content node,
and why will it be changed in the DefaultHandler ?


> Better MimeType Handling
> ------------------------
>
>                 Key: JCR-1172
>                 URL: https://issues.apache.org/jira/browse/JCR-1172
>             Project: Jackrabbit
>          Issue Type: Improvement
>          Components: jackrabbit-webdav
>    Affects Versions: 1.3
>            Reporter: Claus Köll
>            Assignee: angela
>             Fix For: 1.4
>
>
> After saving a Excel File through WebDAV the mimetype will be changed.
> The mimetype for a Win2000 Exel File is application/vnd.ms-excel. This will be changed to application/msexcel.
> Also problems makes the new office 07 format (docx,xlsx,pptx). They will also be changed to application/octet-stream (default mimetype).
> We have a lot of file types that we store in jackrabbit that are not in the properties file (MSInfoPath-, OutlookMsg-, MsAccess-Files, ...)
> I think it will be better to let the mimetype property untouched if a mimetype is present so we must not put all the possible mimetypes in the property file.
> BR
> claus

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Re: [jira] Commented: (JCR-1172) Better MimeType Handling

Posted by Angela Schreiber <an...@day.com>.
hi claus

that question got lost in the second issue.

> what is the recommended nodetype for the jcr:content node

it depends on your needs. we don't have recommendations.
but i can explain 2 needs i know of:

- we changed the default from nt:resource to nt:unstructured
   in order to allow for PROPPATCH. this has been asked for
   by those looking for a flexible dav-server that can deal
   with any kind of custom properties (JCR-416)

- Day's CRX does not required PROPPATCH functionality with
   the dav-server. but we rather wanted to take advantage
   of the 'primary-item-definition'. therefore our default
   is nt:resource.

and there may be additional reasons including for defining
custom nodetypes.

angela