You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@wicket.apache.org by "Alastair Maw (JIRA)" <ji...@apache.org> on 2007/05/24 20:05:17 UTC

[jira] Updated: (WICKET-533) Make sure that Page and no other component requires to load the markup before constructor

     [ https://issues.apache.org/jira/browse/WICKET-533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alastair Maw updated WICKET-533:
--------------------------------

    Fix Version/s:     (was: trunk)
                   1.3.0-rc1

I'm not really sure what this bug means without looking in some depth, but it looks like it needs sorting before rc1.

> Make sure that Page and no other component requires to load the markup before constructor
> -----------------------------------------------------------------------------------------
>
>                 Key: WICKET-533
>                 URL: https://issues.apache.org/jira/browse/WICKET-533
>             Project: Wicket
>          Issue Type: Task
>          Components: wicket
>    Affects Versions: trunk
>            Reporter: Juergen Donnerstag
>             Fix For: 1.3.0-rc1
>
>
> We fixed already one use case (BodyContainer) which loaded the markup "before" the Page constructor was executed. Hence the page parameter could not be used for custom resource loading within the Page's constructor. Check the code and make sure that markup is not loaded before (or call a component method to subclass)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.