Sounds great.
I am just wondering whether it would be better/possible to replace the
MergeResolver with some validation thingy on each entity (throwing
exceptions if validation fails)?
The common merge resolver would probably just assert that state is
valid and fail otherwise. Maybe this could be expressed as some
advanced constraints on the entities themselves (constraints
concerning several properties/entities)?
Med venlig hilsen / Kind regards
Kent Sølvsten
Den 05/05/2009 kl. 04.15 skrev Niclas Hedhman:
On Tue, May 5, 2009 at 10:11 AM, Rickard Öberg
<[email protected]> wrote:
So:
*) refresh() invalidates all EntityState but retains Entity
references
I would like to rename it, since 'refresh' in the new situation is a
bit ambiguous. "invalidateStates()" for instance.
*) new merge() operation replays changes from server on local
entities, but
only if local has not changed. If yes, then ask MergeResolver for
help
Ok.
*) apply() stays, but with logic as outlined in previous post.
Ok.
Cheers
--
Niclas Hedhman, Software Developer
http://www.qi4j.org - New Energy for Java
I live here; http://tinyurl.com/2qq9er
I work here; http://tinyurl.com/2ymelc
I relax here; http://tinyurl.com/2cgsug
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
