|
||||||||||||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||||||||||||
----------------------------------------------------------------
For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: <dev-list-unsubscr...@magnolia-cms.com>
----------------------------------------------------------------
Hi Markus,
Better late than never, indeed it's been an issue to set the VaadinSession's ErrorHandler to null. Fortunately we have come to fix this recently in
MGNLUI-2819(yet to be backported to 5.2.x).For your information, just setting our AdmincentralErrorHandler on the VaadinSession turned out to be less "stable" than when it is on the UI — when an internal error occurred, it would then take at least one more refresh / ?restartApplication to get it back up. So we simply kept Vaadin's DefaultErrorHandler on the session. Doesn't log to the pulse for sure but at least there is a trace in the logs (Vaadin uses java.util.logging.* by the way).
If you don't mind, I'll close this issue as outdated then.
Thanks for reporting anyway!