Re: JDK 1.7 build
I'm not proposing that we change the source to use JDK 1.7 features (not yet, anyway). On Thu, Jun 7, 2012 at 2:13 AM, Massimo Lusetti wrote: > On Tue, Jun 5, 2012 at 6:52 PM, Howard Lewis Ship wrote: > >> Interesting that that one test that fails from the command line (the >> one about template character encoding) works on JDK 1.7. >> >> There's a couple of warnings, and something's gone kablooie in the JavaDoc. >> >> My big concern is how well code generated by the JDK 1.7 compiler, >> even targeting Java 1.5, will work for end-user applications running >> on JDK 1.5 or earlier. Any insights? > > I'm sorry but I still don't have JDK 1.7 on any of my boxes. All of my > clients still run 1.6 and I have always compiled on 1.6 for 1.6 > > Cheers > -- > Massimo > > - > To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org > For additional commands, e-mail: dev-h...@tapestry.apache.org > -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com - To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org For additional commands, e-mail: dev-h...@tapestry.apache.org
Re: Tapestry 5.1.0.5 to 5.2.6 migration. .html templates
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 behavoir in 5.2.6, a behavoir that worked in 5.1.0.5.
locator.locateTemplate fails here.
private Resource locateTemplateResource(ComponentModel initialModel, Locale
locale)
{
ComponentModel model = initialModel;
while (model != null)
{
Resource localized = locator.locateTemplate(model, locale);
if (localized != null)
return localized;
// Otherwise, this component doesn't have its own template ...
lets work up to its
// base class and check there.
model = model.getParentModel();
}
// This will be a Resource whose URL is null, which will be picked
up later and force the
// return of the empty template.
return
initialModel.getBaseResource().withExtension(TapestryConstants.TEMPLATE_EXTENSION);
}
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Tapestry-5-1-0-5-to-5-2-6-migration-html-templates-tp5713624p5713695.html
Sent from the Tapestry - Dev mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org
For additional commands, e-mail: dev-h...@tapestry.apache.org
Re: JDK 1.7 build
On Tue, Jun 5, 2012 at 6:52 PM, Howard Lewis Ship wrote: > Interesting that that one test that fails from the command line (the > one about template character encoding) works on JDK 1.7. > > There's a couple of warnings, and something's gone kablooie in the JavaDoc. > > My big concern is how well code generated by the JDK 1.7 compiler, > even targeting Java 1.5, will work for end-user applications running > on JDK 1.5 or earlier. Any insights? I'm sorry but I still don't have JDK 1.7 on any of my boxes. All of my clients still run 1.6 and I have always compiled on 1.6 for 1.6 Cheers -- Massimo - To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org For additional commands, e-mail: dev-h...@tapestry.apache.org
