[SLING-2898] Failed integration tests for the new Resource Access Tags

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Launchpad Testing 10
• Fix Version/s: Launchpad Testing 10, JCR Resource 2.3.0
• Component/s: API, Testing
• Assignee: Eric Norman
• Reporter: Eric Norman
• Created: 02/Jun/13 20:54
• Updated: 20/Sep/19 11:34
• Resolved: 02/Jun/13 20:56

Description

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.