Reindexing content (via ModeShape's public API) produces a lot of log messages such as the following:

WARN HSEARCH000050: It appears changes are being pushed to the index out of a transaction. 
Register the IndexWorkFlushEventListener listener on flush to correctly manage Collections!

These messages are being logged by Hibernate Search; See ISPN-1218 (which is marked as WONTFIX), but I think we need to address this.

I think the problem is because we're not in a transaction when re-indexing, but the code is stating that we are.