[dna-issues] [JBoss JIRA] Resolved: (DNA-570) JcrObservationManager's Logic For Filtering Events Based On Node Types Is Incorrect

[Dan Florian (JIRA)]

     [ https://jira.jboss.org/jira/browse/DNA-570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dan Florian resolved DNA-570.
-----------------------------

    Resolution: Done


Changed logic of JcrNodeTypeManager.isDerivedFrom method to check if the collection or one or more given types are equal to or derived from the primary type or mixins of the Event node. Uncommented the appropriate tests in JcrObservationManagerTest and JcrTckTest which now run fine.

> JcrObservationManager's Logic For Filtering Events Based On Node Types Is Incorrect
> -----------------------------------------------------------------------------------
>
>                 Key: DNA-570
>                 URL: https://jira.jboss.org/jira/browse/DNA-570
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>    Affects Versions: 0.6
>            Reporter: Dan Florian
>            Assignee: Dan Florian
>             Fix For: 0.7
>
>
> The logic was determining if the Event node's primary type or mixins were equal to or derived from one or more given types. This was backwards and was allowing too many events to get through. The logic should check if the collection or one or more given types are equal to or derived from the primary type or mixins of the Event node. Changes to JcrNodeManager and JcrObservationManager will be needed. And once fixed, uncomment the appropriate tests in JcrObservationManagerTest and JcrTckTest.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira