[
https://issues.apache.org/jira/browse/SLING-85?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger closed SLING-85.
----------------------------------
Resolution: Fixed
Using the JSP script path as the name of the component starting with Rev.
588568.
> JspC: Use JSP script path as component name
> -------------------------------------------
>
> Key: SLING-85
> URL: https://issues.apache.org/jira/browse/SLING-85
> Project: Sling
> Issue Type: Bug
> Components: Plugin
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: 2.0.0
>
>
> Currently the JspC plugin uses the fully qualkified JSP classname (without
> the leading org.apache.jsp package) as the name of the component. This makes
> it difficult to use the JSPs as components and almost prevents seemless
> migration of JSP scripts from repository based (as used in microsling
> currently) to bundle-based as demonstrated in the sample project.
> The fix is to use the JSP script file path as the name of the component. By
> correctly adapting component resolution, a JSP script may thus be stored in
> the repository or in the bundle and always be addressed the same, by its
> script path.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
