You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Eric Norman (JIRA)" <ji...@apache.org> on 2013/06/02 22:58:20 UTC

[jira] [Resolved] (SLING-2898) Failed integration tests for the new Resource Access Tags

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

Eric Norman resolved SLING-2898.
--------------------------------

       Resolution: Fixed
    Fix Version/s: JCR Resource 2.2.10
                   Launchpad Testing 7

fixed in revision 1488784.
                
> Failed integration tests for the new Resource Access Tags
> ---------------------------------------------------------
>
>                 Key: SLING-2898
>                 URL: https://issues.apache.org/jira/browse/SLING-2898
>             Project: Sling
>          Issue Type: Bug
>          Components: API, Testing
>    Affects Versions: Launchpad Testing 7
>            Reporter: Eric Norman
>            Assignee: Eric Norman
>             Fix For: Launchpad Testing 7, JCR Resource 2.2.10
>
>
> The org.apache.sling.launchpad.webapp.integrationtest.scripting.SlingJSPTaglibTest.testTaglib test fails with 2 different errors:
> 1. mkdir(http://localhost:59005/apps/integration-test/taglib-test) failed, status code=409
>    -- this happens when the tests don't run in a specific order.  Some of the parent folders don't exist yet, so it reports an error.  Changing the code to use testClient.mkdirs(..) intstead of testClient.mkdir(..) seems to resolve this issue.
> 2. java.lang.IllegalAccessException: Class javax.el.BeanELResolver can not access a member of class org.apache.sling.jcr.resource.internal.helper.jcr.JcrItemResource with modifiers "public"
>   -- this happens because the EL implementation uses reflection to retrieve the getPath method for the JcrNodeResource class.  However the declaring class for the method (JcrItemResource) was not declared as public, so the reflection code could not read it.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira