You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "angela (JIRA)" <ji...@apache.org> on 2007/10/25 15:38:51 UTC
[jira] Created: (JCR-1188) WebDAV: Allow for Extensions of
MimeResolver in the Configuration.
WebDAV: Allow for Extensions of MimeResolver in the Configuration.
------------------------------------------------------------------
Key: JCR-1188
URL: https://issues.apache.org/jira/browse/JCR-1188
Project: Jackrabbit
Issue Type: New Feature
Components: jackrabbit-webapp, jackrabbit-webdav
Reporter: angela
Assignee: angela
Priority: Minor
Fix For: 1.4
Currently mime type detection is done using the content type header or (if missing) using a static MimeResolver instance in
the IOUtil class. The MimeResolver itself reads from a properties file, that obviously does not list all possible extensions and
mimetypes.
This could be improved by:
- extending the resource configuration.
- extend the ImportContext and ExportContext interfaces
- replacing the current usages of IOUti#MIMERESOLVER by the corresponding calls on the Context classes which
themselves get a MimeResolver that is retrieved from the resource configuration.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (JCR-1188) WebDAV: Allow for Extensions of
MimeResolver in the Configuration.
Posted by "angela (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
angela resolved JCR-1188.
-------------------------
Resolution: Fixed
rev. 588236
> WebDAV: Allow for Extensions of MimeResolver in the Configuration.
> ------------------------------------------------------------------
>
> Key: JCR-1188
> URL: https://issues.apache.org/jira/browse/JCR-1188
> Project: Jackrabbit
> Issue Type: New Feature
> Components: jackrabbit-webapp, jackrabbit-webdav
> Reporter: angela
> Assignee: angela
> Priority: Minor
> Fix For: 1.4
>
>
> Currently mime type detection is done using the content type header or (if missing) using a static MimeResolver instance in
> the IOUtil class. The MimeResolver itself reads from a properties file, that obviously does not list all possible extensions and
> mimetypes.
> This could be improved by:
> - extending the resource configuration.
> - extend the ImportContext and ExportContext interfaces
> - replacing the current usages of IOUti#MIMERESOLVER by the corresponding calls on the Context classes which
> themselves get a MimeResolver that is retrieved from the resource configuration.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.