Thanks again for the response. For the first part I had it already
figured out, but having a concrete example is always helpful.
> We thought the same - but this not manageable with more than 50 files
in one folder. So we decide to use folders - as already mentioned.
Perhaps I'll write a tutor
Hello Edgar,
> I think I'm missing something: since every WebPage in wicket has
straight access to resources located in the web root (that is, every
path reference in the page's markup is relative to the web root)
Wicket is able to locate resources outside of the web application: This
could
Hello Jan, that seems like a good approach. However, I think I'm missing
something: since every WebPage in wicket has straight access to
resources located in the web root (that is, every path reference in the
page's markup is relative to the web root), I would like to avoid using
folders to org
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
Hi Edgar,
Yes, this is the way to go.
On Tue, Dec 4, 2012 at 9: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 the
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, s
