[
https://issues.apache.org/jira/browse/WICKET-6001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14995279#comment-14995279
]
Martin Grigorov commented on WICKET-6001:
-----------------------------------------
I've changed it because it is bad practice to catch Throwable. It will catch
Error too, e.g. OutOfMemoryError, ThreadDeath, VirtualMachineError, and those
are not recoverable.
How this breaks the component queueing?
What happens after the re-throw of the runtime exception?
> Exception raised while refreshing a page with queued components missing in
> the markup
> -------------------------------------------------------------------------------------
>
> Key: WICKET-6001
> URL: https://issues.apache.org/jira/browse/WICKET-6001
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 7.0.0
> Reporter: Palancher aurélien
> Assignee: Andrea Del Bene
> Attachments: myproject.war
>
>
> An exception is raised when refreshing a page or panel containing queued
> components which are missing in the markup.
> We can omit queued components in the markup when the page is created the
> first time but we cannot refresh it
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
