I wanted to say: The Sling classes are still there - only Eclipse classes
are not available anymore. But as those have never been exported, this is
strange to me

Carsten


2014-05-05 16:43 GMT+02:00 Carsten Ziegeler <[email protected]>:

> The sling classes are still, but they have newer been exported, only
> org.apache.sling.scripting.jsp.jasper.runtime is exported - so I'm
> wondering why this fails now?
>
> Carsten
>
>
> 2014-05-05 16:32 GMT+02:00 Bertrand Delacretaz <[email protected]>:
>
> Hi,
>>
>> https://issues.apache.org/jira/browse/SLING-3545 - missing
>> ELContextWrapper/JspValueExpression
>>
>> https://issues.apache.org/jira/browse/SLING-3546 -
>> org.apache.sling.scripting.jsp.jasper.JasperException cannot be
>> resolved
>>
>> I suspect that code refers to classes of the "old" compiler that are
>> gone now, but I'm not sure if we can just fix the code using new /
>> more standard classes instead, or if we have to dig deeper to preserve
>> compatibility with existing code.
>>
>> IOW, are people using these classes in actual JSP code, or do we just
>> have them in our tests?
>>
>> org.apache.sling.scripting.jsp.jasper.el.ELContextWrapper
>> org.apache.sling.scripting.jsp.jasper.el.JspValueExpression
>> org.apache.sling.scripting.jsp.jasper.JasperException
>>
>> -Bertrand
>>
>
>
>
> --
> Carsten Ziegeler
> [email protected]
>



-- 
Carsten Ziegeler
[email protected]

Reply via email to