Castor 1.2 codegen seems to generate too many types, even with org.exolab.castor.builder.javaclassmapping=type (which as I understood is default anyway). If an element of an XSD complex type has a type which has been generated, why then generate wrapper type for the element itself? Hopefully newer versions are better at it.
Regards, Stevo. On Wed, Sep 2, 2009 at 5:18 PM, Jean-Marc Borer <[email protected]> wrote: > Sorry, wrong email manip. > > On Wed, Sep 2, 2009 at 3:15 PM, Stevo Slavić<[email protected]> wrote: > > Jean-Marc Borer, > > > > I don't see how your comment/question relates to my thread. > > > > Please don't steal my thread, create a separate one. Thanks! > > > > Regards, > > Stevo. > > > > On Wed, Sep 2, 2009 at 4:57 PM, Jean-Marc Borer <[email protected]> > 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 > >> > >> --------------------------------------------------------------------- > >> 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 > > >
