-----Original Message----- From: gtk [mailto:gtk@well.com] Subject: [Zope-dev] Pointer-to-Object Properties, ObjectManagers and Z2 Conflicts
Oh, wierd! I just figured out why it's so hard to untangle the relationship between ObjectManagers and their children. The children are stored as attributes of the ObjectManager itself, NOT in a dict. This makes some sense from an acquisition point of view, but probably means that there are a whole bunch of "reserved ids" like manage_beforeDelete.
Error Type: Bad Request Error Value: The id manage_beforeDelete is invalid - it is already in use.
I also feel a little worried that a future version of a class might add a class attribute which clashes with a pre-existing instance attribute added by the user. The protection you describe won't help if the attribute is added in an earlier version, before that class attribute was added. Has anyone else explored this potential problem?