Classes tagged as value object must have a constructor and no setters
To enforce the concept of (immutable) value objects, the class scheme builder should assure that classes which are tagged as properties
- have a constructor method which is used for setting the object's properties
- don't have any setter methods
If these rules are neglected, the persistence framework will run in trouble because it assumes that all values are set after the constructor has been called.
[+FEATURE] FLOW3 (Reflection): When building class schemata the ReflectionService now checks value objects for a constructor and no setters, resolves #6868.
[~TASK] Party: PersonName now has a constructor and no longer any setters.