applied MISC-50; updated @SuppressWarnings references to fully-qualified form in generated files
added support for the generation of an equalProperties(..) method in value objects, this feature is disabled by default though
added value object template merge-point, this allows custom code such as equals()/hashcode() to be merged into value objects
get rid of pointless attribute initialization in default constructor (also it doesn't even use the default values that are set).
avoid null pointer during the copy
fixed doubly generation of constructor if only required parameter is of type "self reference" (unit test file SelfReferencingValueObject.java contained invalid code)
fix bug where correct constructor wasn't being generated.
add serial version UID to serializable enums
Value Object setters are now always public (like before), this is necessary to allow easier interoperation with other cartridges. Use this value object change this to fix SPRING-162 (Conflict between Calendar and Date types on value object constructors) and SPRING-160 (Bug in Generation of Base DAOs toValueObject method)
java and javadoc improvements, fixed HIB-166, JAVA-28, UMLMETA-66 (pluralization support now features languange specific inflectors, currently only English is being used, additional development is requirered to enble i18n on this)
improved last commit by making the setter protected when a property is frozen, all properties are publicly available even when they are flagged as private
added a convenience method for copying other values objects' properties into this one (useful when this object is being listened to and you don't want to replace the instance)
fullyQualifiedName was incorrectly used (should be getterSetterTypeName, so that things like arrays will work).
Merge from V3
improvements to constructor additions, frozen properties are now final for value objects and instances are now constructed as 'good citizens'
improved support for value object constructors (there's a separate constructor for properties that ar erequired and/or read-only, taking care of inherited properties too)
Merge changes from V3
attributes that have a multiplicity > 0 now also have templating support; Value Objects can now be made abstract
added support for 'frozen' value object attributes/associations (meaning they are read-only and won't have a setter method) fixed an issue with templating where subclass elements would not be allowed in orderriding methods (MyClass<? extends T>)
merge from 3.x
Added support for serializing. (Needed for Spring-107)
add defaultValuePresent to the attribute facade, also improve default value support in the JSF cartridge's parameters
fix spacing
add a property for turning off property constructor generation.
Fix JAVA-19 (patch by Jens Vagts)
ordered collections where not handle correctly
don't output the package unless it exists
only output the package if it exists
minor template refactoring
license header mapping (fixes MISC-24 for java)
make the enumerations use the new metafacade literal values, also untabify other templates.
added: serializable namespace property
minor cleanup
cleanup some unused code
add ability to extend value objects
fix another indention
fix some code formatting
change attributes to properties for constructor (so that all attributes/associations are taken into account)
- Add two new templates to the java cartrige, Service and ServiceImpl which will generate POJO Service objects. - Also set "required" attribute to false for all java templates since any combination of them could be used (none should be required). Now if a cartridge user uses the java cartridge they can set the outlets in a namespace for any of the templates they want to use, and all others will be ignored (meaning they won't get the warning exception) - Also move java cartridge templates down a level so they are in "templates/java" (to avoid conflicts with cartridges having templates with the same name).
This form allows you to request diffs between any two revisions of this file. For each of the two "sides" of the diff, select a symbolic revision name using the selection box, or choose 'Use Text Field' and enter a numeric revision.