The transaction for deleting a Classification is wrongfully marked as "readonly". However, the resulting PersistenceException is catched in ClassificationService. The Exception there is not handled correctly.
Todo:
Adjust Integration Tests
Stop marking the tarnsaction as READONLY
Throw an Exception in case a database Exception occurs during deleteClassification in ClassificationService
ryzheboka
commented
4 months ago
The transaction for deleting a Classification is wrongfully marked as "readonly". However, the resulting PersistenceException is catched in ClassificationService. The Exception there is not handled correctly. Todo: