[hibernate-issues] [Hibernate-JIRA] Commented: (EJB-272) PostRemove being called before entity is actually deleted

[ http://opensource.atlassian.com/projects/hibernate/browse/EJB-272?page=co... ] Paul commented on EJB-272: -------------------------- I will try to get a test case when I have time, but here are some steps to prove this: 1. Create an entity that has a foreign key association to a parent entity. 2. Don't do any casading with the associations 3. Create a listener on the child entity containing a method annotated with postremove 4. In this method, use JDBC to delete the parent entity by getting the current entity manager, cast it to the hibernate implementation, and get the current connection. This will fail because of a constraint violation. This is because the child entity has not been deleted from the database yet. An easier test might be to try to load the child entity from the database in the postremove method within the same transaction. I'm using step 4 in my code. The application that I am working on contains some legacy classes and logic where I can't use casacading to delete the parent. -- 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