oship-dev team mailing list archive
-
oship-dev team
-
Mailing list archive
-
Message #01446
Re: [Bug 614863] Re: openehr.Pathable class needs parent() and name() methods
On Wed, 2010-09-01 at 15:34 -0300, Diego Manhães Pinheiro wrote:
> Yes, that's right. The catalog system is connected with certain events
> which is only triggered when you add a object to a container.
> Everytime that you add a object to a object container, events are
> triggered both by container and by the object. The __name__ and
> __parent__ are defined using events. Object are cataloged using other
> events too.
> The point is then you define something on these attributes in a object
> during object initialization time and after that set it in a Grok
> container which IS NOT a Locatable object, the attributes probably will
> be overridden and will generate an weird behavior.
Okay. Thanks for the explanation.
But it still seems to me that once instantiated in memory the __parent__
and __name__ will be correct. The unit/level of persistence in the
reference model is a COMPOSITION. So the Grok machinery should never
touch anything inside the COMPOSITION. Correct?
--Tim
Attachment:
signature.asc
Description: This is a digitally signed message part
References