You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: documentation/2.0/content/concepts/archive.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -69,7 +69,8 @@ The root directory under which JARs/directories used for server classpaths are s
69
69
The root directory under which empty directories must exist for Coherence persistent stores.
70
70
71
71
#### `wlsdeploy/custom`
72
-
This is the root directory where your custom files can be stored in and extracted from the archive. These files are not collected by the Discover Domain Tool. Every file resource under this directory is extracted.
72
+
This is the root directory where your custom files can be stored and extracted from the archive. These files are not collected by the Discover Domain Tool.
73
+
Every file resource under this directory is extracted during `createDomain` and `updateDomain`.
73
74
74
75
#### `wlsdeploy/domainBin`
75
76
The root directory under which `$DOMAIN_HOME/bin` scripts are stored. Only scripts referenced in the `domainInfo/domainBin` section of the model are extracted.
Copy file name to clipboardExpand all lines: documentation/2.0/content/developer/alias-definitions.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -139,7 +139,7 @@ This key element specifies which method should be used for retrieving the value
139
139
By default, an attribute is read write in both WLST and MODEL. This element is used to set an attribute to read-only. The two read-only attributes are `RO` and `ROD`. The latter indicates that the attribute is read-only and will not be written into the domain. However, it will be discovered by the Discover Domain Tool into the model.
140
140
#### `preferred_model_type`
141
141
142
-
This key element specifies the preferred data type that should be used to put data in the model during discovery. As an example, list values can be represented in the model as comma-separated text, such as `"value1, value2"`, or as a YAML list, such as `["value1", "value2"]`. If the list values can contain commas, it is preferred to use a YAML list.
142
+
This key element specifies the preferred data type that should be used to put data in the model during discovery. As an example, list values can be represented in the model as comma-separated text, such as `"value1, value2"`, or as a YAML list, such as `["value1", "value2"]`. If the list values can contain commas, a YAML list must be used.
0 commit comments