You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by "Justin Edelson (JIRA)" <ji...@apache.org> on 2011/04/26 20:43:03 UTC

[jira] [Resolved] (SLING-2057) can't be used across servlet contexts

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

Justin Edelson resolved SLING-2057.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: Scripting JSP 2.0.16
         Assignee: Justin Edelson

> <c:import> can't be used across servlet contexts
> ------------------------------------------------
>
>                 Key: SLING-2057
>                 URL: https://issues.apache.org/jira/browse/SLING-2057
>             Project: Sling
>          Issue Type: Improvement
>          Components: Scripting
>            Reporter: Justin Edelson
>            Assignee: Justin Edelson
>             Fix For: Scripting JSP 2.0.16
>
>
> as discussed here: http://sling.markmail.org/thread/zux7mejcuvegidoe
> there's a ClassCastException when using <c:import> across contexts. The problem is similar to SLING-1928 in that it has to do with the fact that Sling provides a custom JspFactory object. When doing a cross-context import, the default JspFactory should be reset to the container's original.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira