> Is it possible to set the engine up to ALWAYS cull the page pool (and > whatever else it does), so that the single user test case is > representative of the multi-user experience?
That's what "org.apache.tapestry.disable-caching=true" does. Define it as a system property, for example, with a -D option on the command line to your app server. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
