Hi, https://issues.apache.org/jira/browse/WICKET-1974 describes a way to make all URLs absolute. Unfortunately the patch attached to the issue is still not applied so you'll have to build wicket yourself. Regards, Erik. Op 18-06-10 21:56, b...@actrix.gen.nz schreef: Hi Fernando,
Thanks Erik. Why are you using absolute URLS? Are you using absolute URLs to support editing in the web directory, with a directory structure the same as the java package structure, without breaking images? Then it would look like you have found a different solution for the same problem.
Hi, You could have the files in a sibling directory in the web directory that is hidden by the wicket filter mapping. Has many benefits. Allows web developers to freely edit and view files in context with links that actually work. FInally HTML refactoring will work. Can someone suggest how to
The solution I found: application.init getResourceSettings().addResourceFolder(/WEB-INF/html); Your resources will be protected by web-inf and the configuration is the same in local development machine and in the remote development machine, where you can give permits to your web designers. Not
Hi Fernando, obviously quite a few including yourself are separating markup from Java packages to make it accessable to HTML developers. How do you cope with the fact that Wicket markup, when rendered in any folder without flattening the package structure, gets broken images? That is what I am
If you haven't customized the resource locator your telling wicket to look sibling directory to your classpath root WEB-INF/classes which I THINK is where wicket will start looking for resources. It may be easier to use the build helper plugin which handles resources much better than maven does