Aargh . another typo forgot to return the
_myObject
// Lazy initialized object, gets created, fetched, whatever and
cached when the getter is accessed the first time
public Object myObject() {
if ( _myObject == null ) {
_myObject = ..
Typo, sorry . I meant to say "null", not "bull"
OK, scenario.
// Object iVar
Object _myObject;
// Lazy initialized object, gets created, fetched, whatever and
cached when the getter is accessed the first time
public Object myObject() {
if ( _myObject == null ) {
On Aug 25, 2006, at 7:39 AM, Ute Hoffmann wrote:
Hallo,
just a question for clarification again. In my app there are some
big pages (containing a lot of data and html).
The HTML is not relevant. The graph of WOElement and WOComponents
created from the HTML template and WOD file is. Usin
Each entry in the page cache is the top level WOComponent for a page,
by context id. Checking out the references in your WOComponent will
tell you what objects are being retained. So any EOs held in
instance variables, etc.
Paul
On 25 Aug 2006, at 17:46, Kieran Kelleher wrote:
AFAIK, t
AFAIK, the page cache contains WOComponents and the template/wod. The
final HTML is generated each time the response is generated. If you
have memory expensive objects on a page, have them created via lazy
initialization and set the object to bull AFTER append to response is
complete. Then
Hallo,
just a question for clarification again. In my app there are some big
pages (containing a lot of data and html). In the page cache, will
there be only saved a reference and the template or will the html-page
with complete content be saved or is it completely different?
Follow up: If a
