Index: srcgen-properties.xml =================================================================== --- srcgen-properties.xml (Revision 6893) +++ srcgen-properties.xml (Arbeitskopie) @@ -17,114 +17,128 @@
-

Please find below a list of properties that can be set in the - castor-builder.properties file to control various advanced - options of the source generator. By default, the Castor XML code - will look for such a property file in the following places:

+

Please find below a list of properties that can be configured through + the builder configuration properties, as defined in either the default + or a custom XML code generator configuration file. These properties allow you + to control various advanced options of the XML source generator.

+ + + + Option + Description + Values + Default + Since
Version + + + org.exolab.castor.builder.javaVersion + Compliance with Java version + 1.4/5.0 + 1.4 + 1.0.2 + + + org.exolab.castor.builder.boundproperties + Generation of bound properties + true/false + false + 0.8.9 + + + org.exolab.castor.builder.javaclassmapping + Class generation mode + element/type + element + 0.9.1 + + + org.exolab.castor.builder.superclass + Global super class (for all classes generated) + Any valid class name + - + 0.8.9 + + + org.exolab.castor.builder.nspackages + XML namespace to package name mapping + A series of mappings + - + 0.8.9 + + + org.exolab.castor.builder.equalsmethod + Generation of equals method + true/false + false + 0.9.1 + + + org.exolab.castor.builder.primitivetowrapper + Generation of Object wrappers instead of primitives + true/false + false + 0.9.4 + + + org.exolab.castor.builder.automaticConflictResolution + Specifies whether automatic class name conflict resolution + should be used or not + true/false + false + 1.1.1 + + -

    -
  1. If no custom property file is specified, the Castor XML code - generator will use the default builder configuration - properties at - org/exolab/castor/builder/castorbuilder.properties.
    2. -
  2. If a file named castorbuilder.properties is available - on the CLASSPATH, the Castor XML code generator will use each of the - defined property values to override the default value as explained - above. This fiel is commonly referred to as a custom - builder configuration file.
    3. -

- - - - Option - Description - Values - Default - Since
Version - - - org.exolab.castor.builder.javaVersion - Compliance with Java version - 1.4 or 5.0 - 1.4 - 1.0.2 - - - org.exolab.castor.builder.boundproperties - Generation of bound properties - true or false - false - 0.8.9 - - - org.exolab.castor.builder.javaclassmapping - Class generation mode - element or type - element - 0.9.1 - - - org.exolab.castor.builder.superclass - Global super class (for all classes generated) - Any valid class name - - - 0.8.9 - - - org.exolab.castor.builder.nspackages - XML namespace to package name mapping - A series of mappings - - - 0.8.9 - - - org.exolab.castor.builder.equalsmethod - Generation of equals method - true or false - false - 0.9.1 - - - org.exolab.castor.builder.primitivetowrapper - Generation of Object wrappers instead of primitives - true or false - false - 0.9.4 - - -
-
+
+ +

By default, the Castor XML code generator will look for such a property file + in the following places:

-
+

    +
  1. If no custom property file is specified, the Castor XML code + generator will use the default builder configuration + properties at org/exolab/castor/builder/castorbuilder.properties + as shipped as part of the XML code generator JAR.
    2. +
  2. If a file named castorbuilder.properties is available + on the CLASSPATH, the Castor XML code generator will use each of the + defined property values to override the default value as defined + in the default builder configuration properties. This file is commonly + referred to as a custom builder configuration file.
    3. +

+ +
+ +
-

As of Castor 1.0.2, the Castor source generator now supports the - generation of Java 5.0 compliant code. The generated code - with the - new feature enabled - will make use of the following Java 5.0-specific - artifacts: +

+ +

As of Castor 1.0.2, the Castor source generator now supports the + generation of Java 5.0 compliant code. The generated code - with the + new feature enabled - will make use of the following Java 5.0-specific + artifacts: + +

    +
  • Use of parameterized collections, e.g. ArrayList<String>.
    • +
  • Use of @Override annotations with the generated methods + that require it.
    • +
  • Use of @SupressWarnings with "unused" method parameters + on the generated methods that needed it.
    • +
  • Added "enum" to the list of reserved keywords.
    • +

+ +

To enable this feature (off by default), please uncomment the + following property in your custom castorbuilder.properties + file:

+ + +# This property specifies whether the sources generated +# should comply with java 1.4 or 5.0; defaults to 1.4 +org.exolab.castor.builder.javaVersion=5.0 + +
-
    -
  • Use of parameterized collections, e.g. ArrayList<String>.
    • -
  • Use of @Override annotations with the generated methods - that require it.
    • -
  • Use of @SupressWarnings with "unused" method parameters - on the generated methods that needed it.
    • -
  • Added "enum" to the list of reserved keywords.
    • -

- -

To enable this feature (off by default), please uncomment the - following property in your custom castorbuilder.properties - file:

- - - # This property specifies whether the sources generated - # should comply with java 1.4 or 5.0; defaults to 1.4 - org.exolab.castor.builder.javaVersion=5.0 - - -
-

Bound properties are "properties" of a class, which when @@ -147,8 +161,7 @@ created as follows:

- -/** +/** * Registers a PropertyChangeListener with this class. * @param pcl The PropertyChangeListener to register. **/ @@ -289,6 +302,27 @@
+
+

Since version 1.1.1

+ +

With this property enabled, the XML code generator will use + a new automatic class name resolution mode that has special + logic implemented to automatically resolve class name conflicts.

+ +

This new mode deals with various class name conflicts where previously + a binding file had to be used to resolve these conflicts manually.

+ +

To enable this feature (turned off by default), please add the + following property definitio to your custom castorbuilder.properties + file:

+ +# Specifies whether automatic class name conflict resolution +# should be used or not; defaults to false. +# +org.exolab.castor.builder.automaticConflictResolution=true + +
+