Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion documentation/2.0/content/concepts/archive.md
Original file line number Diff line number Diff line change
Expand Up @@ -69,7 +69,8 @@ The root directory under which JARs/directories used for server classpaths are s
The root directory under which empty directories must exist for Coherence persistent stores.

#### `wlsdeploy/custom`
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.
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.
Every file resource under this directory is extracted during `createDomain` and `updateDomain`.

#### `wlsdeploy/domainBin`
The root directory under which `$DOMAIN_HOME/bin` scripts are stored. Only scripts referenced in the `domainInfo/domainBin` section of the model are extracted.
Expand Down
2 changes: 1 addition & 1 deletion documentation/2.0/content/developer/alias-definitions.md
Original file line number Diff line number Diff line change
Expand Up @@ -139,7 +139,7 @@ This key element specifies which method should be used for retrieving the value
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.
#### `preferred_model_type`

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.
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.

#### `wlst_path`

Expand Down