Every time you call IntegrateWithEnvers, there are several ArgumentNullExceptions thrown. They are catched initernally, but if you configure Visual Studio to break on thrown exceptions, you have to turn it off and then on again on start debugging an application. You can reproduce that small problem, if you run one of your tests in debugging mode (or any application that uses Envers, I think).
FYI, if you want to report it to NH Core JIRA, the issue seems to be a composite-id with no defined class.
Tobias Wolschon
October 25, 2012 at 10:57 AM
Thanks for the information!
Roger
October 25, 2012 at 8:29 AM
For other reasons I now sit in a environment using (latest) NH Core and NH Envers source code. I get the same eaten exceptions as you do.
This is a NH Core issue. In my case it's the composite-id (the same would go for a component I guess) that all Envers entities contains - these are dynamic entities (=no class name defined) and NH Core throws/catches exceptions when class is null.
Roger
September 28, 2012 at 9:38 AM
Thank you yourself for your help.
If you come up with any smart ideas why I cannot repro (or you find out the issue is caused by something else), please drop a note here.
Every time you call IntegrateWithEnvers, there are several ArgumentNullExceptions thrown. They are catched initernally, but if you configure Visual Studio to break on thrown exceptions, you have to turn it off and then on again on start debugging an application.
You can reproduce that small problem, if you run one of your tests in debugging mode (or any application that uses Envers, I think).