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/11/06 05:31:44 UTC
[jira] Updated: (SLING-720) Set jcr:mimetype to text/x-java-source
for generated java files
[ https://issues.apache.org/jira/browse/SLING-720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger updated SLING-720:
------------------------------------
Affects Version/s: Commons Mime 2.0.2
Scripting JSP 2.0.2
Affects scripting/jsp because the SlingIOProvider just assigns application/octet-stream to all files created and affactes commons/mime because the .java extension maps to the incorrect MIME type.
> Set jcr:mimetype to text/x-java-source for generated java files
> ---------------------------------------------------------------
>
> Key: SLING-720
> URL: https://issues.apache.org/jira/browse/SLING-720
> Project: Sling
> Issue Type: Bug
> Components: Scripting JSP
> Affects Versions: Commons Mime 2.0.2, Scripting JSP 2.0.2
> Reporter: Dominique Pfister
> Assignee: Felix Meschberger
> Priority: Minor
>
> We have a web-based repository browser that will return nt:files via HTTP with the content-type derived from the jcr:content subnode's jcr:mimeType property. In Sling's JSP Scripting engine, files generated by JSP transpilation/compilation will always have their mime type set to "application/octet-stream" (see org.apache.sling.scripting.jsp.RepositoryOutpuStream). If jcr:mimeType could be changed to "text/x-java-source" for generated java files, they would be displayed directly inside the web browser.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.