looks great. I have been looking into Qi-361 learning some stuff as I go along. The problem is that the prototype used while constructing is the same object that is returned, when the instance is built. The solution is of course to do some copying of state.
There might also be problems regarding too many fragments (concerns/constraints/sideeffects) being applied to a prototype for a Value, which I hope to solve along the way. I will have to look into the old 1.4-behaviour to be sure of that. I still have some problems with state that is not hidden inside properties/associations, but instead stored as mixin state (as in the MapOverrideTest). Am confident to nail it though. Will be off on vacation for 2 weeks, but will resume work when I return from the Caribean :-) /Kent Den 30/05/2012 kl. 16.33 skrev Paul Merlin: > Gang, > > Here is a quick summary of what we did during this week/iteration. > For now, each iteration is one week long and starts/ends on wednesday. > > Work on the website: > - lots of content has been added to the documentation or reworkedfor 2.0 > - dev-status.xml is now exposed on libraries & extensions pages > - CSS has been revamped to fit the asciidoc toolchain output > - the new website is now live and shining on http://qi4j.org > > New library: UoWFile > See http://qi4j.org/library-uowfile.html > > Not so new EntityStore: JClouds returning from the sandbox > See http://qi4j.org/extension-es-jclouds.html > > Appart from that, work started on reviewing the UnitOfWork API and > on fixing QI-361 (ValueBuilder instances can not be reused). > > Please see the Pivotal Tracker mentioned by Niclas to follow and > participate in the effort going on towards Qi4j 2.0. > https://www.pivotaltracker.com/projects/546745 > > @Tibor & al., please feel free to add stories in Pivotal when you contribute. > It's more about keeping our motivation up than tracking our doings. > I hope you get my point :-) > > Regards > > /Paul > > _______________________________________________ > 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
