Small change to how nested attributes are handled with regard to visi…

…bleInForm

dynamo-impl/src/main/java/org/dynamoframework/domain/model/impl/EntityModelFactoryImpl.java

@@ -1109,7 +1109,7 @@ private void setAnnotationCustomOverwrites(Attribute attribute, AttributeModel m
 	private void setAnnotationVisibilityOverrides(Attribute attribute, AttributeModelImpl model, boolean nested) {
 		// set visibility (hide nested attribute by default; they must be shown using
 		// the message bundle)
-		if (attribute.visibleInForm() != null && !VisibilityType.INHERIT.equals(attribute.visibleInForm()) && !nested) {
+		if (attribute.visibleInForm() != null && !VisibilityType.INHERIT.equals(attribute.visibleInForm())) {
 			model.setVisibleInForm(VisibilityType.SHOW.equals(attribute.visibleInForm()));
 		}
 

src/docs/asciidoc/reference.adoc

@@ -209,7 +209,8 @@ also start with “is”, e.g., `isValid()`).
 corresponding to the property. This allows you to create attribute
 models for read-only or composite properties (e.g., a `getNameAndAge()`
 method which concatenates the name and age as a String). Note that such
-an attribute will have to be defined as read-only.
+an attribute will have to be defined as read-only using the "editable"
+setting on the attribute model.
 * Certain attributes are ignored. Currently, this includes only `version`
 (used for JPA optimistic locking) and `class` (as every object has a
 `getClass()` method).
@@ -373,6 +374,10 @@ values:
 enumeration values (`SHOW`/`HIDE`) and the Boolean values `true` and `false`
 are supported.
 
+=== Overrides for nested entities
+
+
+
 == Attribute model settings
 
 In this section, we explain all the supported settings of the attribute