zyro

the "panic" example is just copy/paste from the spring-retry readme ;) in my use-cases it is currently always some sort of error-"logging", which may be just an actual `log.xyz` statement...

@jhoeller our retry exhaustion handling is pretty much specific to each retryable method. for the specific case, what comes to mind are additional `@Retryable` annotation attributes, e.g. a `String retryListener()`...

i do not think that this issue is related to the dirty-checking? the question is rather if/how we can handle an `EntityActionVetoException` now that https://hibernate.atlassian.net/browse/HHH-11721 made it into hibernate-5.2.13?