You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Igor Vaynberg (JIRA)" <ji...@apache.org> on 2008/09/17 18:59:44 UTC
[jira] Resolved: (WICKET-1840) Defaults to ReloadingWicketFilter in
maven's archetype and quickstart
[ https://issues.apache.org/jira/browse/WICKET-1840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Igor Vaynberg resolved WICKET-1840.
-----------------------------------
Resolution: Won't Fix
Assignee: Igor Vaynberg
we are not going to do this. the reloading filter introduces a lot of weirdness once you start adding/removing fields and also causes weird class not found exceptions like cannot cast foo.Bar to foo.Bar
this can turn off a lot of newbies who use the archetype and quickstart and know nothing about the reloading filter or what it does.
> Defaults to ReloadingWicketFilter in maven's archetype and quickstart
> ---------------------------------------------------------------------
>
> Key: WICKET-1840
> URL: https://issues.apache.org/jira/browse/WICKET-1840
> Project: Wicket
> Issue Type: Improvement
> Components: wicket-quickstart
> Affects Versions: 1.3.4, 1.4-M3
> Reporter: Bruno Borges
> Assignee: Igor Vaynberg
> Priority: Trivial
> Fix For: 1.3.5, 1.4-M4
>
>
> The default filter should be ReloadingWicketFilter for both Quickstart and Maven's Archetype projects.
> Both has an web.xml in DEVELOPMENT mode.
> ReloadingWicketFilter could also warn the user to NOT use it when in a DEPLOYMENT mode.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.