WOCachingEnabled caches the parsed component templates. You will still get new instances of components as needed. If you want caching of components, you need to use stateless components or dynamic elements, which can still have multiple copies made depending on what is going on.
On May 1, 2010, at 4:45 AM, Farrukh Ijaz wrote: > Hi, > > I thought setting up -WOCachingEnabled=true enables application to cache > component definitions by default. But why the constructor of the component is > called on every refresh. Some of the components use session object in their > definitions or other methods. But I've also noticed that the refresh to the > page also calls session's constructor. > > How enabling caching can help here? > > Farrukh _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Webobjects-dev mailing list ([email protected]) > Help/Unsubscribe/Update your Subscription: > http://lists.apple.com/mailman/options/webobjects-dev/mschrag%40pobox.com > > This email sent to [email protected] _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
