On Wed, Jun 22, 2011 at 11:30 AM, Rickard Öberg <[email protected]> wrote: > Hi, > > For the 2.0 release I'm considering upgrading from the old JDBM library to > the new JDBM2 one (http://code.google.com/p/jdbm2/). The idea would be to > replace the usage of JDBM straight with JDBM2, but include a migration > service that can copy data from any old JDBM database to a new JDBM2 one. > That would allow for easy migration, and not so much impact on existing > running apps.
+1 on that... > This would be for the entitystore and eventstore based on JDBM. Which reminds me; I think EventObjects and EventStore concepts is something we should try to flesh out and put into a 2.0 as well. Your abstraction of "events" as methods is only one possibility. I found it 'odd' because the 'receiver' is known to the 'sender' so to speak, and that is not always the best model. Would be really good to get together for a day to try and solve this. One part of the issue is that the EventStore needs to be part of the UnitOfWork scoping and commit. I also see that the 'read events' are not required to be within UoW scope, as the events are effectively values, and need a different API and possibly even a different index/query system. Cheers -- Niclas Hedhman, Software Developer http://www.qi4j.org - New Energy for Java I live here; http://tinyurl.com/3xugrbk I work here; http://tinyurl.com/24svnvk I relax here; http://tinyurl.com/2cgsug _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
