ORM called it "concurrent" but its really not. Its just "mutation safe". Talking about its usage of IdentityMap.
And we do actually have a few uses of IdentityMap still left. The problem with IdentityMap was always its use to store entities because we could not rely on their equals/hashcode, so we ended up having to wrap them. Thats what the bytecode stuff gets around; in fact with that stuff we don't even use a collection of any kind anymore, just a hand-maintained linked graph. On 03/18/2013 09:30 AM, Sanne Grinovero wrote: > I don't know about Validator, but in the ORM case at least we didn't > need all the overhead of a concurrent / threadsafe implementation. > > On 18 March 2013 14:21, Emmanuel Bernard <emman...@hibernate.org> wrote: >> Galder's work could very well be an interesting solution where we use >> IdentityMap. >> >> I know ORM has be using it less with the bytecode rework but I think we >> still use it in particular in Hibernate Validator. >> >> _______________________________________________ >> hibernate-dev mailing list >> hibernate-dev@lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/hibernate-dev > _______________________________________________ > hibernate-dev mailing list > hibernate-dev@lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hibernate-dev _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
