You are right, I was able to reproduce it:
https://issues.apache.org/jira/browse/WICKET-4509
Christoph
On 20.04.2012 18:24, Andrew Geery wrote:
An issue I ran into with having Wicket reload the html files in development
mode is that it doesn't seem to work if the path to the html files has
An issue I ran into with having Wicket reload the html files in development
mode is that it doesn't seem to work if the path to the html files has
spaces in it. For example, running under Eclipse with the workspace in
c:\Documents and Settings\... html reloading did not work. Taking the
exact
Aha! This is very interesting. I have the same problems and wrote my own
resource finder, which works ok now. But this would explain what the original
problem is! Should be a fairly easy problem to fix, though.
Tom
On 2012-04-20 18:24, Andrew Geery wrote:
An issue I ran into with having
On Sun, Apr 8, 2012 at 5:38 AM, Bernard bht...@gmail.com wrote:
Hi,
The HTML part is covered if your IDE copies HTML files to the
deployment directory when you save them. Wicket will then pick up this
change and reload the corresponding pages. This works for existing
markup but not for new
I don't use ReloadingWicketFilter, but have pretty good luck reloading
changed HTML and classes by simply running in debug mode in my
IDE. With -Dwicket.configuration=development and running under the
debugger, I can redeploy changes with reload changed classes
(command+F9 in Intellij on OSX; I
Eclipse in debug mode indeed allows for some limited reloading of classes, but
JRebel does a good job and my explicit HTML code seems to work as well. I still
need to test it thoroughly. But none of Wicket's regular tools seem to work and
that amazes me.
Tom
Hi,
The HTML part is covered if your IDE copies HTML files to the
deployment directory when you save them. Wicket will then pick up this
change and reload the corresponding pages. This works for existing
markup but not for new markup that was missing.
The Java classes part can only be handled
I've been fighting this for the past two days, but I'm not succeeding. I'm
using Wicket 1.5.5 on GlassFish 3.1.2 and that runs without a problem. I have
configured
filter-classorg.apache.wicket.protocol.http.ReloadingWicketFilter/filter-class
to reload the classes, but that is not working.
