Hello Edgar, Yes, this is how it works.
For the best separation of the responsibilities, you may store the resources outside of the web application (Think about a complete physical separation). We've made a good experience to break-off with wicket's given package structure - wicket's resource localization does not fit with a separation of the responsibilities: the web designer has no knowledge about the internal package structure and it's not resistant against refactoring. Therefore, we use a more technical mechanism based on style, variation locale and the filename.
1. <prefix>/<style>/<variation>/<locale>/<filename>.<extension> 2. <prefix>/<style>/<variation>/<filename>.<extension> 3. <prefix>/<style>/<filename>.<extension> 4. <prefix>/<filename>.<extension> 5. <filename>.<extension> Best regards, Jan On 12/04/2012 09:04 AM, Edgar Merino wrote:
Hello, I would like our designers to work with a simple folder structure on our application pages markup, and we would like to avoid including java source code files with the files we share with them. What is the best way to do this? I though about implementing a custom ResourceStreamLocator, so I can for instance name our html files using the fqcn e.g. my.company.HomePage.html and placing these files in the default package (under src/main/html for example). Is this the way to go? Thanks in advance, Edgar Merino --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
