-
Task
-
Resolution: Unresolved
-
Major
-
None
-
None
-
None
-
False
-
None
-
False
-
-
-
-
-
-
-
-
The management model resources used to have the "name" attribute, which has been deprecated for a long time because it is redundant as the resource name is already part of the resource address. In EAP 8.1 the deprecated attribute is being removed and we should mention it in Release notes as it can break existing CLI scripts.
Example of a broken script:
EAP 8.0 - ok:
[standalone@embedded /] /subsystem=logging/periodic-rotating-file-handler=FILE2:add(append=true,autoflush=true,enabled=true,file=\{path=server2.log,relative-to=jboss.server.log.dir},level=ALL,name=FILE2,named-formatter=PATTERN,suffix=.yyyy-MM-dd)
{"outcome" => "success"}
EAP 8.1/WildFly - fail:
[standalone@embedded /] /subsystem=logging/periodic-rotating-file-handler=FILE2:add(append=true,autoflush=true,enabled=true,file={path=server2.log,relative-to=jboss.server.log.dir},level=ALL,name=FILE2,named-formatter=PATTERN,suffix=.yyyy-MM-dd)
'name' is not found among the supported properties: [append, autoflush, enabled, encoding, file, filter, filter-spec, formatter, level, named-formatter, suffix]
EAP 8.1/WildFly without the "name" (name=FILE2) attribute - ok:
[standalone@embedded /] /subsystem=logging/periodic-rotating-file-handler=FILE2:add(append=true,autoflush=true,enabled=true,file=\{path=server2.log,relative-to=jboss.server.log.dir},level=ALL,named-formatter=PATTERN,suffix=.yyyy-MM-dd)
{"outcome" => "success"}
The operation has been marked as deprecated since EAP 6.1:
"deprecated" => {
"since" => "1.2.0",
"reason" => "The name attribute should not be used as the handler's address contains the name."
},