[
https://issues.apache.org/jira/browse/JCR-747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-747:
------------------------------
Fix Version/s: 1.3
> TCK: observation tests are too restrictive
> ------------------------------------------
>
> Key: JCR-747
> URL: https://issues.apache.org/jira/browse/JCR-747
> Project: Jackrabbit
> Issue Type: Bug
> Components: JCR TCK
> Affects Versions: 1.0
> Reporter: Marcel Reutegger
> Priority: Minor
> Fix For: 1.3
>
>
> The basic sequence in all observation tests is:
> 1) add listener
> 2) modify workspace
> 3) remove listener
> 4) wait for events on listener
> This sequence forces an implementation to maintain a logical order for
> listener registrations and content changes. In the light of the asynchronous
> nature of observation events this seems too restrictive for certain
> implementations.
> The sequence should be changed to:
> 1) add listener
> 2) modify workspace
> 3) wait for events on listener
> 4) remove listener
> Which is also more intuitive from a user perspective.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
