[
https://issues.apache.org/jira/browse/SLING-3219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bertrand Delacretaz resolved SLING-3219.
----------------------------------------
Resolution: Fixed
Implemented in http://svn.apache.org/r1537534
The test can now be run with a POST from
http://localhost:8888/system/sling/junit/org.apache.sling.launchpad.testservices.serversidetests.ResourceResolverTest.html
, it looks stable in both Jackrabbit and Oak now, but much slower in Oak (33s
vs. 9 on my box). IIUC the slowness is caused by Oak 0.9 having higher latency
in delivering observation events.
> ResourceResolverTest should be an OSGi test case, and use events instead of
> sleep
> ---------------------------------------------------------------------------------
>
> Key: SLING-3219
> URL: https://issues.apache.org/jira/browse/SLING-3219
> Project: Sling
> Issue Type: Bug
> Components: Testing
> Affects Versions: Launchpad Test Services 2.0.6
> Reporter: Bertrand Delacretaz
> Assignee: Bertrand Delacretaz
> Priority: Minor
>
> The ResourceResolverTest is run in a weird way from a JSP script from the
> integration-tests module, which makes it a bit hard to debug and prevents it
> from using JUnit features.
> Also, it uses sleep to wait for mapping changes to be activated. This makes
> it fragile, and it fails sometimes with Oak where observation events are
> currently (V0.9) delivered less often than in Jackrabbit.
> I'll refactor it as a real JUnit test and instead of sleep() use the
> org/apache/sling/api/resource/ResourceResolverMapping/CHANGED event that the
> mapping subsystem delivers to indicate mapping changes.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
