Niclas Hedhman wrote:
Ping!!!I suggest that we remove UnitOfWork.remove() for now, and if there are strong reasons to bring it back we can do that later.
Like you noted, it's the other way round: UoW.remove() should be there and LifeCycle.remove() should be removed.
/Rickard _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
