Stepping back a little, why do you want to cache data from those
entities?
-David
On Mar 19, 2009, at 11:13 AM, Al Byers wrote:
I am moving this post to dev because I see that "extend-entity" does
not
call populateBasicInfo in ModelEntity. I am guessing that there are
properties that you do not want overridden in extend-entity, but I
would
like to override "never-cache".
I see that there is a "setNeverCache", but I don't see when it would
be
called - when are instances of ModelEntity created - couldn't there
be many
of them? When would I apply "setNeverCache"?
Here is what populateBasicInfo sets:
this.entityName =
UtilXml.checkEmpty(entityElement.getAttribute("entity-
name")).intern();
this.tableName =
UtilXml.checkEmpty(entityElement.getAttribute("table-name"),
ModelUtil.javaNameToDbName(this.entityName)).intern();
this.packageName =
UtilXml.checkEmpty(entityElement.getAttribute("package-
name")).intern();
this.defaultResourceName =
UtilXml.checkEmpty(entityElement.getAttribute("default-resource-
name")).intern();
this.dependentOn =
UtilXml.checkEmpty(entityElement.getAttribute("dependent-
on")).intern();
this.doLock =
UtilXml.checkBoolean(entityElement.getAttribute("enable-lock"),
false);
this.noAutoStamp =
UtilXml.checkBoolean(entityElement.getAttribute("no-auto-stamp"),
false);
this.neverCache =
UtilXml.checkBoolean(entityElement.getAttribute("never-cache"),
false);
this.autoClearCache =
UtilXml.checkBoolean(entityElement.getAttribute("auto-clear-cache"),
true);
Plus it sets sequenceBankSize.
How many, if any, of these fields should be callable from "extend-
entity"?
-Al
---------- Forwarded message ----------
From: Al Byers <[email protected]>
Date: Fri, Mar 13, 2009 at 1:10 AM
Subject: Why "never-cache" on OrderHeader and OrderItem?
To: [email protected]
What is the general reason for turning cache off?
Why for OrderHeader and OrderItem, in particular?
Can caching be turned on via "extend-entity"?
thanks for any info.
-Al
