I encountered something very strange: I've put the Border component with its template and the property files under WEB-INF/components and normally Tapestry shouldn't be able to find the .jwc file, right?! But in my custom SpecificationResolverDelegate the method findComponentSpecification() is never called by Tapestry (=> I can't define the template to be used by the component by hand => I get the error message that the template couldn't be found).
With the Home.page and all of it's related files it's different: The method findPageSpecification() gets called and I can provide a custom org.apache.hivemind.Resource to define the new html template location. Sincerly, Andreas --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
