[
https://issues.apache.org/jira/browse/SLING-317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12583698#action_12583698
]
Felix Meschberger commented on SLING-317:
-----------------------------------------
This patch looks good to me can probably be applied.
The JspC plugin currently by default compiles into target/classes which gets
into the root of the bundle. This is not suitable for the
BundleResourceProvider for the moment. I had a prototype for this, which
allowed for prefix mapping when providing bundle resources, such as
/org/apache/jasper/sample=/var/classes/org/apache/jasper/sample
would provide anything under /org/apache/jasper/sample in the bundle to
resources under /var/classes/org/apache/jasper/sample.
Otherwise, we could just compile the JSP classes such that the appear below
/var/classes in the bundle. But then we could not use normal bundle
classloaders to load these JSPs any more. So the path mapping allong above
lines probably is better.
WDYT ?
> Rename /classes to /var/classes
> -------------------------------
>
> Key: SLING-317
> URL: https://issues.apache.org/jira/browse/SLING-317
> Project: Sling
> Issue Type: Improvement
> Reporter: Bertrand Delacretaz
> Priority: Minor
> Attachments: SLING-317.patch
>
>
> Currently the JSP engine uses /classes to store compiled classes, as
> discussed on list this will be moved to /var/classes. The idea is to use /var
> for transient stuff that is not usually "interesting" to developers
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
