I've been out for a few days. Thanks for the excellent responses!
Thanks! That sounds like it just might meet my needs. Now I just need to figure out the binding file - haven't even looked at it yet :) The reason getting this as close to the current javabeans spec is so that the commons beanutils will work with as little overhead as possible and I can dynamically populate a castor object graph based on metadata. I appreciate all of the help! Danny On 9/27/05, Keith Visco <[EMAIL PROTECTED]> wrote: > > Danny, > > You can change the "AsReference" suffix using the > castorbuilder.properties file using the following property: > org.exolab.castor.builder.collections.reference.suffix > > so you should be able to do: > > org.exolab.castor.builder.collections.reference.suffix=MySuffix > > I noticed in the code that it makes sure the length is not empty, > but you might be able to add a space like: > > org.exolab.castor.builder.collections.reference.suffix= \ > > though I haven't tried it. > > You can then use a binding file to alter the name of the generated array > methods (as not to conflict with the collection methods). > > Anyway, we still adopt the old JavaBeans spec where only array access > methods were specified. The extraCollectionMethods was a work-around for > JDO. We definately could use an update on our generated collection methods. > > --Keith > > Danny Collins wrote: > > Thanks Keith! > > > > That comes a little closer. The generated source still doesn't conform > > to the JavaBean spec - which is a getter and setter that matches the > > attribute name. But I may be able to work with what is generated with > > the extra collections attribute set to true. > > > > I'm still up for suggestions if anyone knows of a way to get the > > SourceGenerator to generate java bean compliant code. > > > > Thanks > > Danny > > > > On 9/26/05, Keith Visco <[EMAIL PROTECTED]> wrote: > > > >>Danny, > >> > >>This may provide you with code that looks more like what you want: > >> > >>http://castor.codehaus.org/xml-faq.html#How-can-I-make-the-generated-source-code-more-JDO-friendly? > >> > >>--Keith > >> > >>Danny Collins wrote: > >> > >>>Hello, > >>> > >>>I have just started working with Castor and the source generator. I > >>>am trying to make a nice generic process to adapt one set of objects > >>>to the graph of castor objects and I am getting stuck when it comes to > >>>lists. > >>> > >>>Castor seems to insist on providing a getter and setter that return > >>>and accept an Array of the specific type of objects instead of just > >>>the JavaBean style of getter and setter for the List that it is > >>>interfacing with. > >>> > >>>Is there any way to over come this default behavior and have the > >>>getters and setters generated with List getX() and setX(List)? > >>> > >>> > >>>TIA, > >>>Danny > >>> > >>>------------------------------------------------- > >>>If you wish to unsubscribe from this list, please > >>>send an empty message to the following address: > >>> > >>>[EMAIL PROTECTED] > >>>------------------------------------------------- > >>> > >>> > >> > >> > >>------------------------------------------------- > >>If you wish to unsubscribe from this list, please > >>send an empty message to the following address: > >> > >>[EMAIL PROTECTED] > >>------------------------------------------------- > >> > >> > > > > > > ------------------------------------------------- > > If you wish to unsubscribe from this list, please > > send an empty message to the following address: > > > > [EMAIL PROTECTED] > > ------------------------------------------------- > > > > > > > ------------------------------------------------- > If you wish to unsubscribe from this list, please > send an empty message to the following address: > > [EMAIL PROTECTED] > ------------------------------------------------- > > ------------------------------------------------- If you wish to unsubscribe from this list, please send an empty message to the following address: [EMAIL PROTECTED] -------------------------------------------------
