1 - In Vaadin 7/8 we were able to customize the UI of the error pane with UI.getCurrent().setErrorHandler(…)
With Flow, any UI being done in here doesnt get pushed to the client. Im able to do serverside jobs without any problems. But client side is not affected.
2 - Is there a way to prevent the UI and the Session from being locked when an exception is Thrown. In Vaadin 7/8 when an exception was Thrown, the user could still continue to work with the application. With Flow, when an exception is thrown, the only way to come back is to refresh the page
1 - In Vaadin 7/8 we were able to customize the UI of the error pane with UI.getCurrent().setErrorHandler(…)
With Flow, any UI being done in here doesnt get pushed to the client. Im able to do serverside jobs without any problems. But client side is not affected.
I’m not sure which method you mean here. There is no UI.setErrorHandler(), there is VaadinSession.setErrorHandler. If you are talking about this handler then the reason of absence anything on the client side is below.
2 - Is there a way to prevent the UI and the Session from being locked when an exception is Thrown. In Vaadin 7/8 when an exception was Thrown, the user could still continue to work with the application. With Flow, when an exception is thrown, the only way to come back is to refresh the page
Neither session nor UI is locked after thrown exception is handled.
The reason why UI becomes unresponsive is : when the error is reported to the client side from the server side it sends critical notification (appError) which terminates the application on the client side.
As a result the client side engine doesn’t do its work anymore.
But everything is fine on the server side.
This is the situation which we have at the moment.
Looks like this is something that can be improved.
You may create a ticket about that.