I think I've managed to confuse myself and you at the same time... :)
It happens a lot... :)
I was actually doing this from the start - "registering" the parent
object (in this case the objectStore) with the child (any object created
by the store):
OK.
So having the "child" storing a reference to the "parent" (objectStore) as an instance variable, even if the objectStore is an instance held in the application scope, avoids any problems with page context, yes?
Yes. The bug only affects direct references to "application", "session" - the lookup of the name effectively fails. If you save references to specific data in those scopes, that's safe.
Phew, at the end of all that it looks like I did good in the first place! :D
Yes.
After all that, does it sound like a sensible way to go?
Yeah, sure, I guess... there's always several sensible ways to solve any problem tho' :)
Sean A Corfield -- http://www.corfield.org/blog/
"If you're not annoying somebody, you're not really alive." -- Margaret Atwood
----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email
to [EMAIL PROTECTED] with the word 'unsubscribe cfcdev' in the message of the email.
CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com).
