[
https://issues.apache.org/jira/browse/SLING-3545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-3545.
-------------------------------------
Resolution: Fixed
The wrong class loader writer was used to load the compiled classes. Now the
jsp one is used (again) which fixes this class loading problem.
> SlingJSPTaglibTest fails due to missing ELContextWrapper/JspValueExpression
> ---------------------------------------------------------------------------
>
> Key: SLING-3545
> URL: https://issues.apache.org/jira/browse/SLING-3545
> Project: Sling
> Issue Type: Bug
> Components: Scripting
> Reporter: Bertrand Delacretaz
> Assignee: Carsten Ziegeler
> Fix For: Scripting JSP 2.0.30
>
>
> The SlingJSPTaglibTest (from launchpad/integration-tests) fails, probably due
> to the recent JSP compiler changes, due to the following classes not being
> found.
> I'm not familiar with that code but I suspect those were implementation
> classes that are gone now.
> The failing script is taglib-test.jsp [1].
> {code}
> The type org.apache.sling.scripting.jsp.jasper.JasperException cannot be
> resolved. It is indirectly referenced from required .class files
> org.apache.sling.scripting.jsp.jasper.el.ELContextWrapper cannot be resolved
> to a type
> org.apache.sling.scripting.jsp.jasper.el.JspValueExpression cannot be
> resolved to a type
> {code}
> [1]
> https://svn.apache.org/repos/asf/sling/trunk/launchpad/integration-tests/src/main/resources/integration-test/taglib-test.jsp
--
This message was sent by Atlassian JIRA
(v6.2#6252)
