Re: Nested Editing Contexts
Re: Nested Editing Contexts
- Subject: Re: Nested Editing Contexts
- From: Mike Schrag <email@hidden>
- Date: Wed, 30 May 2007 15:21:58 -0400
You have stumbled upon what I believe to be one of the biggest
weaknesses in EOF, and the solutions are (again, in my opinion)
terrible.
I don't really see this as a big weakness of EOF ... It has to be
able to track changes, and without an editing context, it's not in a
"transaction", and therefore you can't do it. You can usually get
away with this if you're setting non-relationship attributes, but
especially when it comes to relationships to other objects, this just
can't fly.
I put my "constructor" eogenerator templates up on the wikibook page
months ago -- it autogenerates YourEntity.createYourEntity(...) with
the attributes based on all required attributes and all required
relationships. This gives you essentially exactly what you would
expect a constructor to have, but more like a factory sort of pattern
than a traditional constructor.
ms
_______________________________________________
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