[
https://issues.apache.org/jira/browse/SLING-720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12669150#action_12669150
]
James P. White commented on SLING-720:
--------------------------------------
This seems to call for a more general solution for the related problem of the
MIME type for scripts.
{{javax.script.ScriptEngineFactory}} provides {{getMimeTypes() }} and
{{getExtensions()}} which could/should be used to provide the proper mapping
for installed scripts.
> 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
> Fix For: Scripting JSP 2.0.4, Commons Mime 2.0.4
>
>
> 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.
