my personal advice is to stick with wicket's default markup location. we
designed it this way for a lot of reasons you will eventually discover. the
old world way of placing resources is simply not a good idea.
Geoffrey Gallaway wrote:
>
> Hello,
>
> I'm trying to get tomcat and wicket to pick up changes to html files
> and reload them. I thought this was the default behavior of wicket.
> I'm wondering if it's not working because I'm keeping my html files in
> a separate location than beside my java classes:
>
> public class MyApp extends WebApplication {
> @Override
> protected void init() {
> super.init();
>
> addComponentInstantiationListener(new
> SpringComponentInjector(this));
> IResourceSettings resourceSettings = getResourceSettings();
> resourceSettings.addResourceFolder("html/");
> resourceSettings.setResourceStreamLocator(new
> PathStripperLocator());
> resourceSettings.setResourcePollFrequency(Duration.ONE_SECOND);
> }
> }
>
> Am I misunderstanding wicket and tomcat's ability to pick up changes
> to resources on the fly?
>
> Thanks,
> Geoff
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
--
View this message in context:
http://www.nabble.com/Reloading-HTML-resources-on-the-fly--tp16748845p16750981.html
Sent from the Wicket - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
