Hibernate version: Annotations 3.4.0.GA, core-3.3.1.GA


I've discovered that if I have a collection as such:
private List<Content> content;

in a class, and have it mapped as follows:

@OneToMany(mappedBy = "feed", fetch = FetchType.LAZY, cascade = javax.persistence.CascadeType.ALL)
@Cascade(CascadeType.DELETE_ORPHAN)
@Cache(usage = CacheConcurrencyStrategy.NONSTRICT_READ_WRITE)
@OrderBy("displayOrder")
@Where(clause = "active = 1")
public List<Content> getContent() {
if (content == null){
content = new ArrayList<Content>();
}
return content;
}

The where clause is ignored when getting the items. If I remove the @Cache annotation, the where clause is honored. The same happens if I were to add a @LazyCollection(LazyCollectionOption.EXTRA) annotation.

Actually, I figured out why this is happening, still not sure the best way to get around it. But here's what's happening,

Collection initialized into cache with where clause, gives you 3 entries. In the code, you change one of the entries, setting active = false in the example above. Since I didn't actually change the collection, hibernate doesn't know to flush the cache, so the collection cache still returns the entry, even though active = false.

Thoughts on how to get around this?