As I see and exaclty as you refer here: this filtering is feature of the Richfaces UI component not Seam or underlying persistence layer! It is nothing to do with how the working collection is propagated from the database. As you use paging (which is feature of the persistence query) with your query, the specific result set contains only records on the current page. If your intention is to refresh the whole result set on such captured DOM events then you should connect this JS call with your entity query refresh-paging logic...