Helge Weissig wrote: > Hi, > > trying to troubleshoot a particular screen class, I noticed that it > was instantiated 3 times during the access to the page. Looking at the > stack traces, the instantiation seems to happen once for the layout, the > screen, and the page call chains. Is there a reason not to cache the > screen class instance in the context? Is there a place where this is > documented?
See the following cutout of TurbineResources.properties: ---8<--- # ------------------------------------------------------------------- # # M O D U L E C A C H I N G # # ------------------------------------------------------------------- # This determines whether or not to cache the modules in memory. For # development, turn this off. For production, turn this on. # # Default: false # ------------------------------------------------------------------- module.cache=false ---8<--- This works for all module type class instances, such as actions, screens, layouts etc. Note, however, that Turbine keeps only one instance of every module in the cache, so module classes *must be thread-safe* to use this feature. Bye, Thomas. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
