It's something of a remanant from Tapestry 3 and earlier. At one time, it was useful, because you would often subclass BaseEngine in a Tapestry application. Nowadays, that's not a good solution, as you can change behavior using HiveMind instead.
On 1/6/06, Kris Rasmussen <[EMAIL PROTECTED]> wrote: > Can anyone explain to me why tapestry pools engines by locale? I beleive I > looked into this a year or two ago but I can't seem to remember what I found > and I need to know it again ;). From what I remember, all the templates are > fetched from the same pool with the locale included in their multi key so I > don't beleive it has anything to do with templating. Is it because property > language files are stored somewhere in the engine? > > Thanks, > Kris > -- Howard M. Lewis Ship Independent J2EE / Open-Source Java Consultant Creator, Jakarta Tapestry Creator, Jakarta HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
