You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Juergen Donnerstag (JIRA)" <ji...@apache.org> on 2010/01/17 09:43:54 UTC
[jira] Commented: (WICKET-2679) checkRendering() throws Exception
if TransparentResolver is invisible
[ https://issues.apache.org/jira/browse/WICKET-2679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12801344#action_12801344 ]
Juergen Donnerstag commented on WICKET-2679:
--------------------------------------------
I'm not sure yet what the root cause is, but the problem goes away when you remove SimplePanel("childMarkup") from the homepage. Which means the problem could as well be <wicket:container> or a combination of both.
> checkRendering() throws Exception if TransparentResolver is invisible
> ---------------------------------------------------------------------
>
> Key: WICKET-2679
> URL: https://issues.apache.org/jira/browse/WICKET-2679
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.4.1, 1.4.2, 1.4.3, 1.4.4, 1.4.5
> Reporter: Michael Mosmann
> Attachments: de.flapdoodle.bugs--wicket-transparent-resolver.zip
>
>
> When a page has a TransparentResolver which is invisible, then rendering fails, if one child has it's own markup.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.