EclipseLink's support for Continuous Query Notification has the following limitations:
Changes to an object's secondary tables will not trigger them to be invalid unless a @Version annotation is used and updated in the primary table.
Changes to an object's OneToMany, ManyToMany, and ElementCollection relationships will not trigger it to be invalid, unless an @Version annotation is used and updated in the primary table.