Re: Tapestry 5.1.0.5 to 5.2.6 migration. .html templates

2012-06-11 Thread chog
Sorry for posting this in the wrong list. I solved this by decorating ComponentTemplateLocator. -- View this message in context: http://tapestry.1045711.n5.nabble.com/Tapestry-5-1-0-5-to-5-2-6-migration-html-templates-tp5713624p5713769.html Sent from the Tapestry - Dev mailing list archive at

Re: Tapestry 5.1.0.5 to 5.2.6 migration. .html templates

2012-06-08 Thread Lance Java
Firstly, this question should be on the user's list (not the dev list). To change template lookup behaviour, you will need to either override or (more likely) decorate the ComponentResourceLocator.

Re: Tapestry 5.1.0.5 to 5.2.6 migration. .html templates

2012-06-07 Thread chog
I've found that the problem seems to be that ComponentTemplateSourceImpl fails to load MyTemplateLocator.class and insteads load DefaultTemplateLocator/PageTemplateLocator which looks for tml pages in the correct directory, where MyTemplateLocator looks for html pages. How do I override this

Tapestry 5.1.0.5 to 5.2.6 migration. .html templates

2012-06-05 Thread chog
Hi, I'm migrating the tapestry framework of an application from 5.1.0.5 to 5.2.6 and I'm running into problems with locating the .html templates that hold the .tml components. public class MyTemplateLocator implements PageTemplateLocator { private final ComponentClassResolver resolver;