[
https://issues.apache.org/jira/browse/SLING-593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger resolved SLING-593.
-------------------------------------
Resolution: Fixed
The problem is that the JSP compiler defaults ignoring expression language
support if the web.xml file is a pre-Servlet API 2.4 file. This was exactly the
case for the JspC plugin, which had an empty Servlet API 2.3 web.xml file. I
modified the empty web.xml file to be Servlet API 2.4 compliant. Now it seems
to work.
Committed in Rev. 682715 and deployed SNAPSHOT version
2.0.3-incubator-20080805.140521-2.
Please close this bug, if this works for you. Thanks.
> JSPC does not respect JSTL/EL expressions
> -----------------------------------------
>
> Key: SLING-593
> URL: https://issues.apache.org/jira/browse/SLING-593
> Project: Sling
> Issue Type: Bug
> Components: Maven Plugins
> Affects Versions: Maven JSPC Plugin 2.0.2
> Reporter: Honwai Wong
> Assignee: Felix Meschberger
> Attachments: test.jsp
>
>
> When using the JSPC plugin for precompilation of jsp-scripts, contained
> JSTL/EL expressions are ignored and the resulting servlets simply output the
> JSTL/EL expression instead of evaluating the expression itself. The
> precompiled classes are deployed as an OSGi bundle.
> If the exact same script is deployed directly to the target repository (e.g.
> with WebDAV), the JSTL/EL expressions are evaluated correctly.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
