Now returning to my main goal - it is to allow PersistentObject subclasses work correctly on server and cannot be done without changing PersistentObjectHolder's event procession. The only reason that we have those PropertyChangeProcessingStrategy and many threadLocals all around is that PersistentObject-collections must notify context unlike ToMany-collections. So, if we are setting reverse arc via add() or remove() we get infinite loops an other nasty things. We already have readProperty/readPropertyDirectly pair for simple properties, where readPropertyDirectly is "silent". My question is - why can't we have "silent" addTargetDirectly and removeTargetDirectly for to-many properties? This will allow as to manage event cycles. I think this will eliminate threadlocals and make Cayenne code simpler and safer
- Re: Nested ROP contexts and relationships Andrus Adamchik
- Re: Nested ROP contexts and relationships Andrey Razumovsky
- Re: Nested ROP contexts and relationships Robert Zeigler
- Accessing object metadata and other utiliti... Andrus Adamchik
- Re: Accessing object metadata and other... Robert Zeigler
- Re: Accessing object metadata and other... Andrey Razumovsky
- Re: Accessing object metadata and other... Lachlan Deck
- Re: Accessing object metadata and other... Michael Gentry
- Re: Nested ROP contexts and relationships Andrus Adamchik
- Re: Nested ROP contexts and relationships Andrey Razumovsky
- Re: Nested ROP contexts and relationshi... Andrey Razumovsky
- Re: Nested ROP contexts and relationshi... Andrey Razumovsky
- Re: Nested ROP contexts and relationshi... Andrus Adamchik
- Re: Nested ROP contexts and relationshi... Andrey Razumovsky
- Re: Nested ROP contexts and relationshi... Andrus Adamchik
- Re: Nested ROP contexts and relationshi... Andrey Razumovsky
- Re: Nested ROP contexts and relationshi... Andrus Adamchik
- Re: Nested ROP contexts and relationshi... Andrey Razumovsky
- Re: Nested ROP contexts and relationshi... Andrus Adamchik
- DO/PO design Andrus Adamchik
- Re: DO/PO design Tore Halset
