[
https://issues.apache.org/jira/browse/WICKET-6001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14995360#comment-14995360
]
Andrea Del Bene commented on WICKET-6001:
-----------------------------------------
Well, I think the title of this issue is a little bit misleading. The problem
is not about component queueing working bad. The really problem is that the
exception is not re-throw and, as a result, it goes unnoticed by user.
If the same exception (thrown by MarkupContainer#onDetach) occurs during
rendering phase, it's correctly displayed to user. I just asked you if my
proposed change could break something you did in your commit.
> 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)
