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-class>org.apache.wicket.protocol.http.ReloadingWicketFilter</filter-class>
to reload the classes, but that is not working. The only way to reload the
class file is by using JRebel.
Also Wicket reports that it runs in DEVELOPMENT mode, but it is not reloading
the HTML files. In an attempting to resolve that I explicitely configured
getResourceSettings().setDefaultCacheDuration(Duration.ONE_SECOND);
but that does not make a difference. The only way I can get it to work
somewhat, is to add my own ResourceFinder directly on the src folder:
getResourceSettings().setResourceFinder(new IResourceFinder()
{
@Override
public IResourceStream find(Class<?> clazz, String pathname)
{
File f = new File("C:/Documents and Settings/User/My
Documents/s2m/sources/components/service/src/main/java/" + pathname);
if (f.exists())
{
return new FileResourceStream( f );
}
return null;
}
});
getResourceSettings().setUseDefaultOnMissingResource(true);
But still the source are not reloaded reliably. I figure if the cache expires,
a new call to the resource finder should be done, correct?
Is there any debugging of these autoreload features, so I can see what Wicket
is doing?
Tom
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
