[
https://issues.apache.org/jira/browse/SLING-1315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-1315.
-------------------------------------
Resolution: Fixed
We fixed some issues in the latest jsp scripting and the jcr class loader; I
think this is fixed now.
If it still happens for you with latest trunk, please open a new bug
> java.lang.ClassNotFoundException during jsp compilation
> -------------------------------------------------------
>
> Key: SLING-1315
> URL: https://issues.apache.org/jira/browse/SLING-1315
> Project: Sling
> Issue Type: Bug
> Components: Scripting
> Environment: Day CQ5.2.1 fresh installation
> Reporter: zhangchunlong
> Attachments: errors.log
>
>
> This problems occurs only in this situations:
> * first time compilation of all the JSPs being used by a CQ Template
> * it happens only for requests to JSPs that generate CSS fragments.
> perhaps this is a timing issue because they are compiled at the same time
> when requested simulatneously by the browser.
> To reproduce this issue, please following the "steps to reproduce" in the
> DayCare ticket [1] .
> 1. for page [2], you could delete the contents under "jcr:content" to avoid
> unnecessary errors. The template codes generate the errors.
> 2. there is a easier way to reproduce the error which is connect to WebDAV
> and delete the compiled class file at /var/classes/org/.... and refresh the
> page again.
> 3. it is not happen every time, but most of time, when it happens, there is a
> .classtmp file generated for the corresponding JSP under /var/classes/org/....
> [1]
> http://daycare.day.com/home/volkswagen/volkswagen_de/vwcms_design/16481.html
> [2] http://localhost:4502/de_sample/brand/de/e5_content.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
