You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Dan Klco (JIRA)" <ji...@apache.org> on 2014/06/12 21:39:02 UTC

[jira] [Resolved] (SLING-3664) TEI Classes Breaking Integration Tests

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

Dan Klco resolved SLING-3664.
-----------------------------

    Resolution: Fixed

Fixed in 1602275, Updated to have class fallbacks for adaptTo and getProperty

> TEI Classes Breaking Integration Tests
> --------------------------------------
>
>                 Key: SLING-3664
>                 URL: https://issues.apache.org/jira/browse/SLING-3664
>             Project: Sling
>          Issue Type: Bug
>          Components: Scripting
>    Affects Versions: Scripting JSP-Taglib 2.2.0
>            Reporter: Dan Klco
>            Assignee: Dan Klco
>             Fix For: Scripting JSP-Taglib 2.2.2
>
>
> It seems like the addition of the TagExtraInfo (TEI) classes in SLING-3475 is causing the integration tests to fail.  You can reproduce this by running the integration tests at sling-builder/launchpad/integration-tests with:
> mvn test -Dtest=SlingJSPTaglibTest
> It seems like the issue is that the TEI classes provide more information to the JSP compiler which causes it to compile the code differently.  While this might possibly improve performance it leads to some different behavior.  Previously, when you attempted to adapt an object into a class which did not exist, you would get null.  Now it actually causes the JSP to fail to compile.



--
This message was sent by Atlassian JIRA
(v6.2#6252)