Hi all, I've read through the majority of the Tapestry 5 documentation and implemented a few samples to make sure I understand how things work. There are a few specific tasks I couldn't figure out and would appreciate if anyone could shed some light...
1) Is there a way to localize page classes? The page templates and message bundles work great but nothing I tried worked for localized classes. If page class localization is currently unsupported, is that a feature that may be accepted for inclusion into the main framework distribution if a patch was donated? 2) Is there a way to override an internal service implementation? As a work-around for #1 above, I attempted to define a build method for ClassNameLocator, which understandably resulted in an exception since it had already been defined. None of the decorate methods I came up with succeeded, although I was able to decorate what I bound to the ServiceBinder in my own 'AppModule' class. 3) Is there a way to 'inherit' from a base template in a localized template and only override certain sections? I didn't see a way to do this, although I definitely understand how the <t:body/> was used for creating a wrapper template. As an example, one could define a header with a unique id in a base template and have a localized version that displays everything the same except for the header. If you've ever used Facelets, I'd envision something similar to using <ui:insert name='title'>Default Content</> in the base template and in the localized template: <ui:composition template='parent-template.xhtml'>, where the template attribute specifies the 'parent' template and contains an override in the form of: <ui:define name='title'>New Content</>. I may be missing some obvious things here; any thoughts would be much appreciated. Thanks, -Keith --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
