Yes, we use Web modules so that resources such as Tapestry page/component specifications get copied over to their respective locations under the exploded WAR directory at project compile time.
We also find it very useful to start our servlet container with the org.apache.tapestry.disable-caching system property set to true to force Tapestry to load specifications from the file system at development time.
Yes, we use Web modules so that resources such as Tapestry page/component specifications get copied over to their respective locations under the exploded WAR directory at project compile time.
We also find it very useful to start our servlet container with the org.apache.tapestry.disable-caching system property set to true to force Tapestry to load specifications from the file system at development time.
Hope it helps.