[hibernate-issues] [Hibernate-JIRA] Issue Comment Edited: (HHH-6960) NullPointerException in PreCollectionRemove Listener

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-6960?page=c... ] Marek Dominiak edited comment on HHH-6960 at 1/20/12 7:36 AM: -------------------------------------------------------------- In our appliaction we have got this exception as well with exactly the same stack trace. I was trying to prepare a test case but unfortunately it seems to be really hard. For all simple cases (simple domain model) exception is not throws, for our complicated case (quite big domain model) this exception is thrown for some use cases when we try to delete complicated set of somehow connected entities. To create test case I would have to copy 50+ classes which was taking too much time. I have tried to change the source code to add additional check for null: @Override public void onPreRemoveCollection(PreCollectionRemoveEvent event) { CollectionEntry collectionEntry = getCollectionEntry( event ); if ( collectionEntry != null && collectionEntry.getLoadedPersister() != null && !collectionEntry.getLoadedPersister().isInverse() ) { onCollectionAction( event, null, collectionEntry.getSnapshot(), collectionEntry ); } } and it seems that this change helped. All entities we want to create revisions for were created. Some observations while playing with this issue: - it does not matter how many times @Autited is used - whether one or many entities/fields are annotated with @Autited I get exactly the same results when running our tests each time, I get no errors only when all of @Audited are commented out. So that could be either: our configuration or the bug which causes the exception under certain circumstances (how our entities are connected with each other etc.) UPDATE: I forgot to write that I the same results I got when using Mysql and H2. Our application and configuration worked well with version: 3.6.4.Final. I have tried to use hibernate in version 4.0.1.Final. (we have to remain with 3.6.4.Final) was (Author: marekdominiak): In our appliaction we have got this exception as well with exactly the same stack trace. I was trying to prepare a test case but unfortunately it seems to be really hard. For all simple cases (simple domain model) exception is not throws, for our complicated case (quite big domain model) this exception is thrown for some use cases when we try to delete complicated set of somehow connected entities. To create test case I would have to copy 50+ classes which was taking too much time. I have tried to change the source code to add additional check for null: @Override public void onPreRemoveCollection(PreCollectionRemoveEvent event) { CollectionEntry collectionEntry = getCollectionEntry( event ); if ( collectionEntry != null && collectionEntry.getLoadedPersister() != null && !collectionEntry.getLoadedPersister().isInverse() ) { onCollectionAction( event, null, collectionEntry.getSnapshot(), collectionEntry ); } } and it seems that this change helped. All entities we want to create revisions for were created. Some observations while playing with this issue: - it does not matter how many times @Autited is used - whether one or many entities/fields are annotated with @Autited I get exactly the same results when running our tests each time, I get no errors only when all of @Audited are commented out. So that could be either: our configuration or the bug which causes the exception under certain circumstances (how our entities are connected with each other etc.) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira