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: site/config-overrides.md
+4-3Lines changed: 4 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -182,13 +182,14 @@ The secret macro `SECRETNAME` field must reference the name of a Kubernetes secr
182
182
**Check each item below to ensure custom situational configuration takes effect:**
183
183
184
184
* Reference the name of the current bean and each parent bean in any hierarchy you override.
185
+
* Note that the `combine-mode` verbs (`add` and `replace`) should be omitted for beans that are already defined in your original domain home configuration.
185
186
* See [Override template samples](#override-template-samples) for examples.
186
187
* Use situational config `replace` and `add` verbs as follows:
187
-
* If you are adding a new bean that doesn't already exist in your original domain home `config.xml`, specify `add` on the MBean itself and on each attribute within the bean.
188
+
* If you are adding a new bean that doesn't already exist in your original domain home configuration, specify `add` on the MBean itself and on each attribute within the bean.
188
189
* See the `server-debug` stanza in [Override template samples](#override-template-samples) below for an example.
189
-
* If you are adding a new attribute to an existing bean in the domain home `config.xml`, the attribute needs an `add` verb.
190
+
* If you are adding a new attribute to an existing bean in the domain home configuration, the attribute needs an `add` verb.
190
191
* See the `max-message-size` stanza in [Override template samples](#override-template-samples) below for an example.
191
-
* If you are changing the value of an existing attribute within a domain home `config.xml`, the attribute needs a `replace` verb.
192
+
* If you are changing the value of an existing attribute within a domain home configuration, the attribute needs a `replace` verb.
192
193
* See the `public-address` stanza in [Override template samples](#override-template-samples) below for an example.
193
194
* When overriding `config.xml`:
194
195
* The XML namespace (`xmlns:` in the XML) must be exactly as specified in [Override template schemas](#override-template-schemas).
0 commit comments