Yes please, do that. I the meantime we downloaded the sources 1.3.1 and modified Castor generation to completely eliminate the CylcleBreaker stuff. Everything runs smoothly in our multithreaded applications since then.
I already talk a little bit about that topic at http://jira.codehaus.org/browse/CASTOR-2746 On Wed, Sep 2, 2009 at 8:20 PM, Werner Guttmann<[email protected]> wrote: > Hi Jean-Marc, > > CycleBreaker seems to me a class designed to deal with improving code > generation for hashCode() methods. As far as I remember, it has been a > contribution of a user some years ago. > > As far as I can tell, it related to > > http://jira.codehaus.org/browse/CASTOR-2012 > > Having said that, I am more than happy to e.g. allow users to disable > this code portion during code generation by exposing a new property. > > Regards > Werner > > Jean-Marc Borer wrote: >> Hello castor users, >> >> Can someone explain what CycleBreaker is used for? Appart, from >> bugging and creating memory leaks, I don't see its usefulness. >> >> We had problems when moving from 0.9.4 to 1.3.1. So we simply removed >> everything related to CycleBreaker in the XML generation and all our >> problems are gone... >> >> Cheers, >> >> Jean-Marc >> >> PS: Sorry for replying with this mail >> >> --------------------------------------------------------------------- >> To unsubscribe from this list, please visit: >> >> http://xircles.codehaus.org/manage_email >> >> > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
