Mmh, in Neo semantics, these are calles ProActiveEvents (synchroneous) and ReactiveEvents (asynch, acting as a poor mans side effects :). Not sure it applies here, but ProActive and ReActive cut it quite well for my taste.
/peter On Fri, May 9, 2008 at 8:04 AM, Niclas Hedhman <[EMAIL PROTECTED]> wrote: > On Fri, May 9, 2008 at 2:38 AM, Rickard Öberg <[EMAIL PROTECTED]> wrote: > >> In order to get this going as easily and flexibly as possible I >> therefore added the following method to UnitOfWork: >> void registerUnitOfWorkSynchronization(UnitOfWorkSynchronization >> synchronization); > > I think that either; > > a) Don't require the registration, and instead let UoW explicitly > know of a MixinType that signals the callback. > > or > > b) Allow anyone to register synch callbacks, in which case the > Entity instance must also be passed in the sync calls. > > > IMHO, I think that a) is the better choice for validation and that we > introduce the "Specification" or "Contract" separately for > cross-Entity checks and other rules not possible in a "per Entity" > point of view. > > Also, UnitOfWorkSynchronization? Is that descriptive? I can't come up > with a better name, but asking the many lurkers to chip in. > > Cheers > Niclas > > _______________________________________________ > qi4j-dev mailing list > [email protected] > http://lists.ops4j.org/mailman/listinfo/qi4j-dev > > -- GTalk: neubauer.peter Skype peter.neubauer ICQ 18762544 GTalk neubauer.peter Phone +46704 106975 LinkedIn http://www.linkedin.com/in/neubauer http://www.neo4j.org - New Energy for Data - the Graph Database. http://www.ops4j.org - New Energy for OSS Communities - Open Participation Software. http://www.qi4j.org - New Energy for Java - Domain Driven Development. _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
