[
https://issues.apache.org/jira/browse/JCR-1393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Köll closed JCR-1393.
---------------------------
Resolution: Duplicate
hi angela,
thanks for the informations. ok i think with JCR-1188 i'm able to fix my
problems with unknown mimetypes.
i think also its a logical consequence that there can be problems with webdav
if the node was not added with webdav itself.
so i do not think its a good idea to change the nodetype because it can be a
complex failure search in the future
if we automatically replace a nodetype from a node that was set programatically
!
> Unknown Mimetype should not be set automatically to application/octet-stream
> ----------------------------------------------------------------------------
>
> Key: JCR-1393
> URL: https://issues.apache.org/jira/browse/JCR-1393
> Project: Jackrabbit
> Issue Type: Bug
> Components: jackrabbit-webdav
> Affects Versions: 1.4
> Reporter: Claus Köll
> Attachments: patch.txt
>
>
> if i add a node to jackrabbit i add the jcr:content node as nt:resource.
> if i open now this document with webdav i found that the DefaultHandler
> looks if the jcr:content node is from type nt:unstructured, if not
> the child properties of the content node will be deleted and the properties
> will be set again.
> so there is a problem with the mimetype. if i do that with a office 07
> document (.docx)
> the original mimetype "application/msword" will be changed to
> "application/octet-stream".
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
