Hello Guys,
I ran into a problem this week, when trying to implement this concept http://forevr.tumblr.com/post/1726359751/speedy-unit-tests-using-transactions in my integration tests, which wraps each test in a transaction, and then rolls it back once complete, this preserves the test datas integrity and stops it getting polluted when running tests, and also makes your integration tests run much quicker.
The error I was getting was that when it was running rollback() on the teardown, it said the transaction had not been started. After some Googling around, this is a common message when the transaction has already been committed and closed.
It seems that this is due to a conflict of interest in the way that the BaseORMService, and therefore the VirtualEntityService works with transactions on save.
Has anyone got any suggestions on ways to get around this? I had always thought that transactions could be nested, is that not the case in this approach?
Robert