You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Felix Meschberger (JIRA)" <ji...@apache.org> on 2008/02/27 23:46:51 UTC

[jira] Created: (SLING-286) Use ServletContext to resolve content type of uploaded file

Use ServletContext to resolve content type of uploaded file
-----------------------------------------------------------

                 Key: SLING-286
                 URL: https://issues.apache.org/jira/browse/SLING-286
             Project: Sling
          Issue Type: Bug
            Reporter: Felix Meschberger
            Assignee: Felix Meschberger
             Fix For: 2.0.0


The ujax file upload support currently uses the MimeTypeService to find out the content type of an uploaded file if no such type is explicitly set. This creates a dependency on the MimeTypeService, requires checking for service availability and more. Better would be for the file upload functionality to use the ServletContext of the UjaxPostServlet to resolve the content type.

In fact, the ServletContext of the UjaxPostServlet uses the MimeTypeService for content type resolution, so we still use the full Sling functionality of content type resolution.

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


[jira] Updated: (SLING-286) Use ServletContext to resolve content type of uploaded file

Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/SLING-286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Felix Meschberger updated SLING-286:
------------------------------------

    Component/s: ujax

> Use ServletContext to resolve content type of uploaded file
> -----------------------------------------------------------
>
>                 Key: SLING-286
>                 URL: https://issues.apache.org/jira/browse/SLING-286
>             Project: Sling
>          Issue Type: Bug
>          Components: ujax
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
>             Fix For: 2.0.0
>
>
> The ujax file upload support currently uses the MimeTypeService to find out the content type of an uploaded file if no such type is explicitly set. This creates a dependency on the MimeTypeService, requires checking for service availability and more. Better would be for the file upload functionality to use the ServletContext of the UjaxPostServlet to resolve the content type.
> In fact, the ServletContext of the UjaxPostServlet uses the MimeTypeService for content type resolution, so we still use the full Sling functionality of content type resolution.

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


[jira] Closed: (SLING-286) Use ServletContext to resolve content type of uploaded file

Posted by "Carsten Ziegeler (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/SLING-286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carsten Ziegeler closed SLING-286.
----------------------------------

    Resolution: Fixed

> Use ServletContext to resolve content type of uploaded file
> -----------------------------------------------------------
>
>                 Key: SLING-286
>                 URL: https://issues.apache.org/jira/browse/SLING-286
>             Project: Sling
>          Issue Type: Bug
>          Components: ujax
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
>             Fix For: 2.0.0
>
>
> The ujax file upload support currently uses the MimeTypeService to find out the content type of an uploaded file if no such type is explicitly set. This creates a dependency on the MimeTypeService, requires checking for service availability and more. Better would be for the file upload functionality to use the ServletContext of the UjaxPostServlet to resolve the content type.
> In fact, the ServletContext of the UjaxPostServlet uses the MimeTypeService for content type resolution, so we still use the full Sling functionality of content type resolution.

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