You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Felix Meschberger (JIRA)" <ji...@apache.org> on 2017/02/22 14:53:44 UTC

[jira] [Commented] (SLING-6548) Provide framework extension fragment for Servlet JSP API

    [ https://issues.apache.org/jira/browse/SLING-6548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15878370#comment-15878370 ] 

Felix Meschberger commented on SLING-6548:
------------------------------------------

I am not sure, this is a good idea !

JSP API must be isolated from the environment as we implement our own stuff in Sling. "Inheriting" from the environment means, that we are starting to mix environmental API with implementation requirements.

If you want to leverage the JSP API from the environment this must be properly "coupled" to the actual JSP implementation. So, what you might investigate is actually trying to replace the Jasper implementation (as part of the Scripting JSP bundle) with the JSP API implementation from the environment -- but this would require proper hooking into that implementation for the Scripting JSP bundle to still work !

> Provide framework extension fragment for Servlet JSP API
> --------------------------------------------------------
>
>                 Key: SLING-6548
>                 URL: https://issues.apache.org/jira/browse/SLING-6548
>             Project: Sling
>          Issue Type: New Feature
>          Components: Extensions
>            Reporter: Oliver Lietz
>             Fix For: Framework Extension Fragment Servlet JSP API 1.0.0
>
>
> fragment for {{javax.servlet.jsp}} (Servlet JSP API)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)