|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
It is happening to me. I code around it by overriding the jpa remove method and pulling everything out of the collections there, rather than using the @PreRemove lifecycle method. Especially a mess in my case because I am using a 3 way join table with a compound key. I have A, B, and C, with Integer PKs, and JoinClass, with a compound pk containing the PKs of A, B, and C. And A, B, and C contain collections of JoinClass. So much easier to deal with this in @PreRemove in JoinClass than in the individual remove methods for A, B, and C. If it only worked.