The JCR spec mandates that an update after a session save() is immediately visible to JCR queries after save() [0]. This is true for normal property updates. So your code looks fine.
The exception are full text index updates i.e. from binary files, which are done asynchronously if they are too slow (> X ms I think), as the full text extraction should not block things - it isn't something that a programmatic query (that you might have directly after a session.save()) could rely on anyway. [0] http://www.day.com/specs/jcr/2.0/6_Query.html#6.5%20Search%20Scope Cheers, Alex
