[ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-342?pag... ] Emmanuel Bernard commented on HSEARCH-342: ------------------------------------------ Hi Grégoire, I did not run your test case, as I think Entity2 is lacking @DocumentId, @IndexedEmbedded etc But I am almost certain that you are hitting HSEARCH-178 HSEARCH-178 is not a bug per se but rather a misuse of Hibernate. You must run your operations inside a transaction otherwise it's like having wild sex wo condom, you're on your own. Anyway, we made it a bit safer with HSEARCH-178 I'll mark this bug as duplicate. Please check with 3.1.1 or what's in trunk now. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-342?pag... ] Grégoire Rolland commented on HSEARCH-342: ------------------------------------------ Hi Emmanuel, Thank for your comment. But : 1/ Entity2 is not lacking @DocumentId, I read the doc again and again (my english is very poor, but ...) : "In fact since the 3.1.0 release of Hibernate Search @DocumentId is optional in the case where an @Id annotation exists." 2/ Entity2 is not lacking @IndexedEmbedded, see the "entity1" association. 3/ From Hibernate Entity Manager Doc : "In an EXTENDED persistence context, all read only operations of the entity manager can be executed outside a transaction (find(), getReference(), refresh(), and read queries). Some modifications operations can be executed outside a transaction, but they are queued until the persistence context join a transaction. This is the case of persist(), merge(), remove(). Some operations cannot be called outside a transaction: flush(), lock(), and update/delete queries.". This is the case of the attached test. I attach a second testcase with all the operation in a transaction, the result is the same. 4/ I check 3.1.1-GA, the problem occurs alway. 5/ Please read and run my testcase and if I misuse hibernate say me where. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira