How is this related to the "automaticConflictResolution" flag I set in my castorbuilder.properties file?
Can this "ClassNameConflictResolver" property be set in the Ant task or the SourceGeneratorMain command line? Is this the same as the "name conflict strategy" that I see in the SourceGeneratorMain from this latest 1.1.1 snapshot? I don't understand the syntax for the "namingXML" element in the documentation. How do you specify a global suffix for all complex types using this? > -----Original Message----- > From: Werner Guttmann [mailto:[EMAIL PROTECTED] > Sent: Sunday, April 01, 2007 11:04 AM > To: [email protected] > Subject: Re: [castor-user] Conflict Resolution Strategy: Add > "Type" to type name class? > > There already is. The SourceGenerator has a new method > setClassNameConflictResolver(String) that allows you to set one fo two > values: "xpath" or "type" (with xpath being the default). > > Once you have selected that "type" strategy, in case of a > conflict, the type name of the element being analyzed > currently will be appended to the element name after by a 'By' suffix. > > Werner > > PS If your question is about named complex type vs. element > clashes, please use the binding fiel to specify a global > suffix for all e.g. > complex types. > > Karr, David wrote: > > Would it be possible to define a Conflict Resolution Strategy which > > would cause a type name class that is the same as an > element name to > > get "Type" appended to the end of the class name? > > > > > --------------------------------------------------------------------- > > 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
