ERXThreadStorage and willUpdate()
ERXThreadStorage and willUpdate()
- Subject: ERXThreadStorage and willUpdate()
- From: David Avendasora <email@hidden>
- Date: Mon, 4 Oct 2010 16:22:52 -0400
Hi all,
We are moving from having to remember to manually set the modifiedBy and modifiedDate values in our EOs when they are modified to overriding willUpdate() and pulling the loggedInUser from ERXThreadStorage.
We are overriding willUpdate() in our K12GenericRecord which all our EOs extend.
for example (very simplified to get the point across) :
willUpdate() {
super.willUpdate();
setModifiedBy((SystemUser) ERXThreadStorage.valueForKey("loggedInUser"));
}
As you can see, we are casting the results of the ThreadStorage as SystemUser which itself is a subclass of K12GenericRecord.
It seems odd to be importing a subclass into it's own superclass, but it since a SystemUser really is a standard EO and therefor is-a K12GenericRecord, it also seems correct.
We're not doing anything horribly wrong here, are we?
Dave _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden