anonymous wrote : I'll look up the "after transaction" event in the CVS. It must have been a freshly added one, as it's not listed in the Seam 2B docs... yet. It's not new at all, it's been used in the booking demo for a while. Events.instance().raiseAfterTransactionSuccessEvent(...) anonymous wrote : As you can see, refresh() resets the resultList to null all right, yet the next time query gets accessed, it still contains the same old result list Probably because the transaction is not yet committed and so the new data is not yet flushed by Hibernate to the database. Either: * flush the session manually OR * use an after transaction success event to call refresh View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4065874#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...