feature request #5356open
Handle exceptions which require reconnect
There are some exceptions which should 'never' occur in remoting, but when they do the safest option is to perform a reconnect.
org.hibernate.LazyInitializationException: could not initialize proxy - no Session
java.lang.IllegalStateException: An entity copy was already assigned to a different entity
In the case of these exception, we should popup a cdm error dialog. with the extra hint to the user to reconnect.
Updated by Andreas Müller about 1 year ago
- Description updated (diff)
- Target version changed from Remoting 6.0 to Release 5.19
- Private changed from Yes to No
moving this open remoting 6.0 ticket to current milestone to decide what to do with it.
Is the above mentioned solution really possible?