On 7/30/07, Julian Klappenbach <[EMAIL PROTECTED]> wrote: > There is one con with embedding HTML within jars: if you're not using an > exploded deployment, you have to redeploy in order to make changes in HTML. > For larger project, this can be a waste of time. However, exploded > deployments should negate this drawback.
I believe you should always do a proper rebuild though. Tampering with templates directly is pretty dangerous if you ask me. I think it's just a matter of properly setting up your development street. What I can agree with is that it can seem weird to designers to have to look at deeply nested structures. One resource locator implementation that would help is for instance on that discards the first x directories of a package (e.g. com.mycomp.myproject) so that it isn't as deeply nested. On top of that, it could start looking at the base directory, so that if you e.g. have com.mycomp.myproject.auth.pages.LoginPage, web designers could just find this LoginPage in the root dir. If your project isn't too large, this might make things easier. If other developers don't disagree with this too much, we could create an example that does this, and maybe even ship the resource locator as optional with the wicket core project. Eelco
