[
https://issues.apache.org/jira/browse/WICKET-5438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sven Meier resolved WICKET-5438.
--------------------------------
Resolution: Invalid
Assignee: Sven Meier
This isn't a problem of non-found markup:
With <wicket:child> in your BasePage's markup, subclasses can provide
additional markup, but they don't have to.
In development configuration Wicket rightfully reports the non-rendered
component "title" for HomePage.
In deployment configuration, this check is not performed, see
Application#configure(). You can change this default in your application's
init() with IDebugSettings#setComponentUseCheck(true).
> Empty page without error with missing markup in deployment mode
> ---------------------------------------------------------------
>
> Key: WICKET-5438
> URL: https://issues.apache.org/jira/browse/WICKET-5438
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 6.12.0
> Environment: Windows XP, JDK 1.7, Tomcat
> Reporter: bernard
> Assignee: Sven Meier
> Attachments: quickstart.zip
>
>
> The attached test case dos not produce an error when run in deployment mode.
> May be it should have an error because the markup file is not found.
> I am getting used to the fact that Wicket is type safe with no runtime
> surprises.
> I was quite perplexed when I debugged the page constructor and while I did
> not realize that the markup file wasn't found. As the title says, this
> happens only in deployment mode.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
