2011/3/1 Boudreau, Pierre <[email protected]>: > Thanks for the quick response Antonio. I do have a quick and easy patch that > works for our situation where we are not using Tiles for localization at all. > I added an init parameter to disable localization and only use NULL_LOCALE > whenever definitions are requested from CachingLocaleUrlDefinitionDAO.
I think that a completely different DAO would be better. > It would be nice to get this into the next 2.1 release so that we don't have > to maintain our own custom version of the source. There won't be any 2.1.x release, only 2.2.x is maintained. > I haven't checked if the same patch could be merged in to the trunk as it is, >but it's a pretty small change so it probably could. Shall I send the patch >to you directly or is there a more appropriate place to send it? Create a JIRA issue and attach it. We can discuss it in the issue itself: https://issues.apache.org/jira/browse/TILES However nothing prevents you from using a customized DAO for your needs, given the correct configuration: http://tiles.apache.org/2.1/framework/tutorial/configuration.html > I also attempted a more complete solution that modified > CachingLocaleUrlDefinitionDAO to cache the definitions for all locales more > efficiently by using the same objects when the is no localization instead of > creating and storing a new identical object for each of them. It all looked > good when unit testing it, but it didn't reduce the memory consumption when I > ran it through our load tests and I couldn't figure out why... You can post it as "non official" patch and discuss it, maybe at Tiles Developers mailing list: http://tiles.apache.org/mail-lists.html Thanks Antonio
