Package them as Tapestry Libraries. Mark J. Stang Senior Engineer/Architect office: +1 303.468.2900 mobile: +1 303.507.2833 Ping Identity
-----Original Message----- From: Steve Shucker [mailto:[EMAIL PROTECTED] Sent: Thu 11/2/2006 4:59 PM To: Tapestry users Subject: Changing template locations Is there a way to change the location where tapestry looks for html templates? I've got a component library project with a standard maven2 file structure. I'm writing specless components. I've created a /src/main/webapp directory containing a basic *.application and web.xml file and I use the maven jetty plugin to test. However, running this project as a webapp requires me to move my *.html files into /src/main/webapp/WEB-INF. I'd much rather configure hivemind to look for these files under the classpath where the *.java files are located and packaged for the component library. A SpecificationResolverDelegate doesn't appear to address this issue - the fact that my component backing classes are in the classpath is causing tapestry to assume the *.html files are in WEB-INF. I'd prefer to add an additional search location, but I'd settle for putting another hivemodule.xml in my test WEB-INF folder to search the classpath instead of WEB-INF. -Steve --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
