[
https://issues.apache.org/jira/browse/WICKET-4242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13201239#comment-13201239
]
Martin Grigorov commented on WICKET-4242:
-----------------------------------------
There is a comment at org.apache.wicket.markup.MarkupCache#onMarkupNotFound()
that if the user application needs this feature then it has to override this
method.
I guess it was made this way because otherwise it makes the application slower
by trying to load the missing resource for each web request.
> Detect new Markup Files in Development Mode
> -------------------------------------------
>
> Key: WICKET-4242
> URL: https://issues.apache.org/jira/browse/WICKET-4242
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
> Affects Versions: 1.5.3
> Reporter: bernard
>
> An extension of
> http://www.wicketframework.org/faqs.html#how-reload-changed-markup-files
> Let Wicket detect new markup files not only modifications to existing ones.
> This is useful if a developer fails to add a markup file. That causes an
> exception. Currently the application has to be re-deployed to fix this
> condition.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
