[jira] Resolved: (SLING-1928) JSP API classes from the environment can't be used.

["Carsten Ziegeler (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SLING-1928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carsten Ziegeler resolved SLING-1928.
-------------------------------------

    Resolution: Fixed

Fixed in Revision 1057642.

Instead of registering our own factory, we register a delegate which returns the already set factory in all cases, except when we are inside a jsp call in the jsp scripting.

> JSP API classes from the environment can't be used.
> ---------------------------------------------------
>
>                 Key: SLING-1928
>                 URL: https://issues.apache.org/jira/browse/SLING-1928
>             Project: Sling
>          Issue Type: Bug
>          Components: Scripting
>    Affects Versions: Scripting JSP 2.0.12
>            Reporter: Carsten Ziegeler
>            Assignee: Carsten Ziegeler
>             Fix For: Scripting JSP 2.0.14
>
>
> The jsp scripting bundles includes the jsp api and taglib classes; however if the api classes from "outside" (like another bundle or the servlet engine) should be used instead, this leads to class cast exceptions as the jsp scripting bundle sets the JspFactory.setDefaultFactory() to its own factory. After this call, all web applications of the servlet engine will use the Sling JspFactory which leads to such exceptions

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.