Skip to content

Instantly share code, notes, and snippets.

Show Gist options
  • Select an option

  • Save kabir/6903809 to your computer and use it in GitHub Desktop.

Select an option

Save kabir/6903809 to your computer and use it in GitHub Desktop.
EAP 6.2 and 7.2.0 standalone model comparison
Enter legacy AS version: 7.2.0.Final
Using target model: 7.2.0.Final
Enter type [S](standalone)/H(host)/D(domain)/F(domain + host):S
Read from target directory or from the legacy-models directory - t/[l]:
Report on differences in the model when the management versions are different? y/[n]: y
Not reporting on differences in the model when the management versions are different
Loading legacy model versions for 7.2.0.Final....
Loaded legacy model versions
Loading model versions for currently running server...
Oct 9, 2013 5:11:52 PM org.xnio.Xnio <clinit>
INFO: XNIO Version 3.0.7.GA-redhat-1
Oct 9, 2013 5:11:52 PM org.xnio.nio.NioXnio <clinit>
INFO: XNIO NIO Implementation Version 3.0.7.GA-redhat-1
Oct 9, 2013 5:11:52 PM org.jboss.remoting3.EndpointImpl <clinit>
INFO: JBoss Remoting version 3.2.16.GA-redhat-1
Loaded current model versions
Loading legacy resource descriptions for 7.2.0.Final....
Loaded legacy resource descriptions
Loading resource descriptions for currently running STANDALONE...
Loaded current resource descriptions
Starting comparison of the current....
====== Comparing core models ======
====== Resource root address: [] - Current version: 1.5.0; legacy version: 1.4.0 =======
--- Problems for relative address to root []:
Missing parameters for operation 'read-operation-names' in current: []; missing in legacy [access-control]
Missing parameters for operation 'read-resource-description' in current: []; missing in legacy [access-control]
Different 'type' for 'reply-properties' for operation 'whoami'. Current: STRING; legacy: undefined
Missing child names for type=core-service in current: []; missing in legacy [patching, module-loading]
--- Problems for relative address to root ["core-service" => "management"]:
Missing child types in current: []; missing in legacy [access]
--- Problems for relative address to root ["core-service" => "management","security-realm" => "*"]:
Missing attributes in current: []; missing in legacy [map-groups-to-roles]
Missing parameters for operation 'add' in current: []; missing in legacy [map-groups-to-roles]
Missing child names for type=authorization in current: []; missing in legacy [ldap]
--- Problems for relative address to root ["core-service" => "platform-mbean"]:
Missing child names for type=type in current: []; missing in legacy [buffer-pool]
--- Problems for relative address to root ["core-service" => "platform-mbean","type" => "class-loading"]:
Missing attributes in current: []; missing in legacy [object-name]
Different 'unit' for attribute 'loaded-class-count'. Current: undefined; legacy: "NONE"
Different 'unit' for attribute 'total-loaded-class-count'. Current: undefined; legacy: "NONE"
Different 'unit' for attribute 'unloaded-class-count'. Current: undefined; legacy: "NONE"
--- Problems for relative address to root ["core-service" => "platform-mbean","type" => "compilation"]:
Missing attributes in current: []; missing in legacy [object-name]
--- Problems for relative address to root ["core-service" => "platform-mbean","type" => "garbage-collector","name" => "*"]:
Missing attributes in current: []; missing in legacy [object-name]
Different 'unit' for attribute 'collection-count'. Current: undefined; legacy: "NONE"
Different 'nillable' for attribute 'name'. Current: true; legacy: false
--- Problems for relative address to root ["core-service" => "platform-mbean","type" => "memory"]:
Missing attributes in current: []; missing in legacy [object-name]
Different 'unit' for attribute 'object-pending-finalization-count'. Current: undefined; legacy: "NONE"
--- Problems for relative address to root ["core-service" => "platform-mbean","type" => "memory-manager","name" => "*"]:
Missing attributes in current: []; missing in legacy [object-name]
Different 'nillable' for attribute 'name'. Current: true; legacy: false
--- Problems for relative address to root ["core-service" => "platform-mbean","type" => "memory-pool","name" => "*"]:
Missing attributes in current: []; missing in legacy [object-name]
Different 'unit' for attribute 'collection-usage-threshold-count'. Current: undefined; legacy: "NONE"
Different 'nillable' for attribute 'name'. Current: true; legacy: false
Different 'unit' for attribute 'usage-threshold-count'. Current: undefined; legacy: "NONE"
--- Problems for relative address to root ["core-service" => "platform-mbean","type" => "operating-system"]:
Missing attributes in current: []; missing in legacy [object-name]
Different 'unit' for attribute 'available-processors'. Current: undefined; legacy: "NONE"
--- Problems for relative address to root ["core-service" => "platform-mbean","type" => "runtime"]:
Missing attributes in current: []; missing in legacy [object-name]
Different 'nillable' for attribute 'name'. Current: true; legacy: false
--- Problems for relative address to root ["core-service" => "platform-mbean","type" => "threading"]:
Missing attributes in current: []; missing in legacy [object-name]
Different 'unit' for attribute 'daemon-thread-count'. Current: undefined; legacy: "NONE"
Different 'unit' for attribute 'peak-thread-count'. Current: undefined; legacy: "NONE"
Different 'unit' for attribute 'thread-count'. Current: undefined; legacy: "NONE"
Different 'unit' for attribute 'total-started-thread-count'. Current: undefined; legacy: "NONE"
--- Problems for relative address to root ["deployment" => "*","subdeployment" => "*","subsystem" => "datasources","data-source" => "*"]:
Different 'default' for attribute 'enabled'. Current: false; legacy: true
--- Problems for relative address to root ["deployment" => "*","subdeployment" => "*","subsystem" => "datasources","xa-data-source" => "*"]:
Different 'default' for attribute 'enabled'. Current: false; legacy: true
--- Problems for relative address to root ["deployment" => "*","subdeployment" => "*","subsystem" => "ejb3","entity-bean" => "*"]:
Missing attributes in current: []; missing in legacy [methods]
--- Problems for relative address to root ["deployment" => "*","subdeployment" => "*","subsystem" => "ejb3","message-driven-bean" => "*"]:
Missing attributes in current: []; missing in legacy [methods, delivery-active]
Missing operations in current: []; missing in legacy [stop-delivery, start-delivery]
--- Problems for relative address to root ["deployment" => "*","subdeployment" => "*","subsystem" => "ejb3","singleton-bean" => "*"]:
Missing attributes in current: []; missing in legacy [methods]
--- Problems for relative address to root ["deployment" => "*","subdeployment" => "*","subsystem" => "ejb3","stateful-session-bean" => "*"]:
Missing attributes in current: []; missing in legacy [methods, passivated-count, total-size, cache-size]
--- Problems for relative address to root ["deployment" => "*","subdeployment" => "*","subsystem" => "ejb3","stateless-session-bean" => "*"]
:
Missing attributes in current: []; missing in legacy [methods]
--- Problems for relative address to root ["deployment" => "*","subdeployment" => "*","subsystem" => "messaging","hornetq-server" => "*"]:
Missing attributes in current: []; missing in legacy [active]
Different 'storage' for attribute 'clustered'. Current: "configuration"; legacy: "runtime"
Missing parameters for operation 'add' in current: []; missing in legacy [clustered]
--- Problems for relative address to root ["deployment" => "*","subsystem" => "datasources","data-source" => "*"]:
Different 'default' for attribute 'enabled'. Current: false; legacy: true
--- Problems for relative address to root ["deployment" => "*","subsystem" => "datasources","xa-data-source" => "*"]:
Different 'default' for attribute 'enabled'. Current: false; legacy: true
--- Problems for relative address to root ["deployment" => "*","subsystem" => "ejb3","entity-bean" => "*"]:
Missing attributes in current: []; missing in legacy [methods]
--- Problems for relative address to root ["deployment" => "*","subsystem" => "ejb3","message-driven-bean" => "*"]:
Missing attributes in current: []; missing in legacy [methods, delivery-active]
Missing operations in current: []; missing in legacy [stop-delivery, start-delivery]
--- Problems for relative address to root ["deployment" => "*","subsystem" => "ejb3","singleton-bean" => "*"]:
Missing attributes in current: []; missing in legacy [methods]
--- Problems for relative address to root ["deployment" => "*","subsystem" => "ejb3","stateful-session-bean" => "*"]:
Missing attributes in current: []; missing in legacy [methods, passivated-count, total-size, cache-size]
--- Problems for relative address to root ["deployment" => "*","subsystem" => "ejb3","stateless-session-bean" => "*"]:
Missing attributes in current: []; missing in legacy [methods]
--- Problems for relative address to root ["deployment" => "*","subsystem" => "messaging","hornetq-server" => "*"]:
Missing attributes in current: []; missing in legacy [active]
Different 'storage' for attribute 'clustered'. Current: "configuration"; legacy: "runtime"
Missing parameters for operation 'add' in current: []; missing in legacy [clustered]
====== Comparing subsystem models ======
====== Resource root address: ["subsystem" => "cmp"] - Current version: 1.1.0; legacy version: 1.1.0 =======
====== Resource root address: ["subsystem" => "datasources"] - Current version: 1.2.0; legacy version: 1.1.1 =======
--- Problems for relative address to root []:
Missing parameters for operation 'get-installed-driver' in current: []; missing in legacy [driver-name]
Missing value-type for 'reply-properties' for operation 'get-installed-driver' in current: []; missing in legacy [jdbc-compliant, module-slo
t, driver-class-name, driver-module-name]
--- Problems for relative address to root ["data-source" => "*"]:
Different 'default' for attribute 'enabled'. Current: false; legacy: true
--- Problems for relative address to root ["data-source" => "ExampleDS"]:
Different 'default' for attribute 'enabled'. Current: false; legacy: true
--- Problems for relative address to root ["xa-data-source" => "*"]:
Different 'default' for attribute 'enabled'. Current: false; legacy: true
====== Resource root address: ["subsystem" => "deployment-scanner"] - Current version: 1.0.0; legacy version: 1.0.0 =======
====== Resource root address: ["subsystem" => "ee"] - Current version: 1.0.0; legacy version: 1.0.0 =======
====== Resource root address: ["subsystem" => "ejb3"] - Current version: 1.2.1; legacy version: 1.2.0 =======
====== Resource root address: ["subsystem" => "infinispan"] - Current version: 1.4.1; legacy version: 1.4.0 =======
--- Problems for relative address to root ["cache-container" => "*","distributed-cache" => "*"]:
Different 'alternatives' for attribute 'segments'. Current: ["virtual-nodes"]; legacy: undefined
Different 'alternatives' for attribute 'virtual-nodes'. Current: ["segments"]; legacy: undefined
Different 'alternatives' for parameter 'segments' of operation 'add'. Current: ["virtual-nodes"]; legacy: undefined
Different 'alternatives' for parameter 'virtual-nodes' of operation 'add'. Current: ["segments"]; legacy: undefined
====== Resource root address: ["subsystem" => "jacorb"] - Current version: 1.3.0; legacy version: 1.2.0 =======
====== Resource root address: ["subsystem" => "jaxr"] - Current version: 1.2.0; legacy version: 1.2.0 =======
====== Resource root address: ["subsystem" => "jaxrs"] - Current version: 1.0.0; legacy version: 1.0.0 =======
====== Resource root address: ["subsystem" => "jca"] - Current version: 1.2.0; legacy version: 1.2.0 =======
====== Resource root address: ["subsystem" => "jdr"] - Current version: 1.2.0; legacy version: 1.1.0 =======
====== Resource root address: ["subsystem" => "jgroups"] - Current version: 1.2.0; legacy version: 1.2.0 =======
====== Resource root address: ["subsystem" => "jmx"] - Current version: 1.3.0; legacy version: 1.1.0 =======
--- Problems for relative address to root []:
Missing attributes in current: []; missing in legacy [non-core-mbean-sensitivity]
Missing parameters for operation 'add' in current: []; missing in legacy [non-core-mbean-sensitivity]
Missing child types in current: []; missing in legacy [configuration]
====== Resource root address: ["subsystem" => "jpa"] - Current version: 1.2.0; legacy version: 1.2.0 =======
====== Resource root address: ["subsystem" => "jsf"] - Current version: 1.0.0; legacy version: 1.0.0 =======
====== Resource root address: ["subsystem" => "jsr77"] - Current version: 1.0.0; legacy version: 1.0.0 =======
====== Resource root address: ["subsystem" => "logging"] - Current version: 1.3.0; legacy version: 1.2.0 =======
--- Problems for relative address to root ["async-handler" => "*"]:
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'not' for attribute 'filter'. Curren
t: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'not' for attribute 'filter'. Curren
t: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'not' for attribute 'filter'. Current: false; legacy: true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'not' for value-type key 'any' for a
ttribute 'filter'. Current: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'not' for value-type key 'any' for a
ttribute 'filter'. Current: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'not' for value-type key 'any' for attribute 'filter'. Current: false; le
gacy: true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'any' for attribute 'filter'. Curren
t: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'any' for attribute 'filter'. Curren
t: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'any' for attribute 'filter'. Current: false; legacy: true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for attribute 'filter'. Current: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for attribute 'filter'. Current: false; legacy: true
Different 'nillable' for value-type key 'match' for attribute 'filter'. Current: false; legacy: true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'not' for value-type key 'all' for a
ttribute 'filter'. Current: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'not' for value-type key 'all' for a
ttribute 'filter'. Current: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'not' for value-type key 'all' for attribute 'filter'. Current: false; le
gacy: true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'all' for attribute 'filter'. Curren
t: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'all' for attribute 'filter'. Curren
t: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'all' for attribute 'filter'. Current: false; legacy: true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'not' for parameter 'filter' of oper
ation 'add'. Current: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'not' for parameter 'filter' of oper
ation 'add'. Current: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'not' for parameter 'filter' of operation 'add'. Current: false; legacy:
true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'not' for value-type key 'any' for p
arameter 'filter' of operation 'add'. Current: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'not' for value-type key 'any' for p
arameter 'filter' of operation 'add'. Current: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'not' for value-type key 'any' for parameter 'filter' of operation 'add'.
Current: false; legacy: true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'any' for parameter 'filter' of oper
ation 'add'. Current: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'any' for parameter 'filter' of oper
ation 'add'. Current: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'any' for parameter 'filter' of operation 'add'. Current: false; legacy:
true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for parameter 'filter' of operation 'add'. Current: fal
se; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for parameter 'filter' of operation 'add'. Current: fal
se; legacy: true
Different 'nillable' for value-type key 'match' for parameter 'filter' of operation 'add'. Current: false; legacy: true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'not' for value-type key 'all' for p
arameter 'filter' of operation 'add'. Current: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'not' for value-type key 'all' for p
arameter 'filter' of operation 'add'. Current: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'not' for value-type key 'all' for parameter 'filter' of operation 'add'.
Current: false; legacy: true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'all' for parameter 'filter' of oper
ation 'add'. Current: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'all' for parameter 'filter' of oper
ation 'add'. Current: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'all' for parameter 'filter' of operation 'add'. Current: false; legacy:
true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'not' for parameter 'filter' of oper
ation 'update-properties'. Current: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'not' for parameter 'filter' of oper
ation 'update-properties'. Current: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'not' for parameter 'filter' of operation 'update-properties'. Current: f
alse; legacy: true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'not' for value-type key 'any' for p
arameter 'filter' of operation 'update-properties'. Current: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'not' for value-type key 'any' for p
arameter 'filter' of operation 'update-properties'. Current: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'not' for value-type key 'any' for parameter 'filter' of operation 'updat
e-properties'. Current: false; legacy: true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'any' for parameter 'filter' of oper
ation 'update-properties'. Current: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'any' for parameter 'filter' of oper
ation 'update-properties'. Current: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'any' for parameter 'filter' of operation 'update-properties'. Current: f
alse; legacy: true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for parameter 'filter' of operation 'update-properties'
. Current: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for parameter 'filter' of operation 'update-properties'
. Current: false; legacy: true
Different 'nillable' for value-type key 'match' for parameter 'filter' of operation 'update-properties'. Current: false; legacy: true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'not' for value-type key 'all' for p
arameter 'filter' of operation 'update-properties'. Current: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'not' for value-type key 'all' for p
arameter 'filter' of operation 'update-properties'. Current: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'not' for value-type key 'all' for parameter 'filter' of operation 'updat
e-properties'. Current: false; legacy: true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'all' for parameter 'filter' of oper
ation 'update-properties'. Current: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'all' for parameter 'filter' of oper
ation 'update-properties'. Current: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'all' for parameter 'filter' of operation 'update-properties'. Current: f
alse; legacy: true
--- Problems for relative address to root ["console-handler" => "*"]:
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'not' for attribute 'filter'. Curren
t: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'not' for attribute 'filter'. Curren
t: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'not' for attribute 'filter'. Current: false; legacy: true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'not' for value-type key 'any' for a
ttribute 'filter'. Current: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'not' for value-type key 'any' for a
ttribute 'filter'. Current: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'not' for value-type key 'any' for attribute 'filter'. Current: false; le
gacy: true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'any' for attribute 'filter'. Curren
t: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'any' for attribute 'filter'. Curren
t: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'any' for attribute 'filter'. Current: false; legacy: true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for attribute 'filter'. Current: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for attribute 'filter'. Current: false; legacy: true
Different 'nillable' for value-type key 'match' for attribute 'filter'. Current: false; legacy: true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'not' for value-type key 'all' for a
ttribute 'filter'. Current: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'not' for value-type key 'all' for a
ttribute 'filter'. Current: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'not' for value-type key 'all' for attribute 'filter'. Current: false; le
gacy: true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'all' for attribute 'filter'. Curren
t: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'all' for attribute 'filter'. Curren
t: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'all' for attribute 'filter'. Current: false; legacy: true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'not' for parameter 'filter' of oper
ation 'add'. Current: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'not' for parameter 'filter' of oper
ation 'add'. Current: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'not' for parameter 'filter' of operation 'add'. Current: false; legacy:
true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'not' for value-type key 'any' for p
arameter 'filter' of operation 'add'. Current: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'not' for value-type key 'any' for p
arameter 'filter' of operation 'add'. Current: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'not' for value-type key 'any' for parameter 'filter' of operation 'add'.
Current: false; legacy: true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'any' for parameter 'filter' of oper
ation 'add'. Current: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'any' for parameter 'filter' of oper
ation 'add'. Current: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'any' for parameter 'filter' of operation 'add'. Current: false; legacy:
true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for parameter 'filter' of operation 'add'. Current: fal
se; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for parameter 'filter' of operation 'add'. Current: fal
se; legacy: true
Different 'nillable' for value-type key 'match' for parameter 'filter' of operation 'add'. Current: false; legacy: true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'not' for value-type key 'all' for p
arameter 'filter' of operation 'add'. Current: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'not' for value-type key 'all' for p
arameter 'filter' of operation 'add'. Current: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'not' for value-type key 'all' for parameter 'filter' of operation 'add'.
Current: false; legacy: true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'all' for parameter 'filter' of oper
ation 'add'. Current: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'all' for parameter 'filter' of oper
ation 'add'. Current: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'all' for parameter 'filter' of operation 'add'. Current: false; legacy:
true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'not' for parameter 'filter' of oper
ation 'update-properties'. Current: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'not' for parameter 'filter' of oper
ation 'update-properties'. Current: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'not' for parameter 'filter' of operation 'update-properties'. Current: f
alse; legacy: true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'not' for value-type key 'any' for p
arameter 'filter' of operation 'update-properties'. Current: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'not' for value-type key 'any' for p
arameter 'filter' of operation 'update-properties'. Current: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'not' for value-type key 'any' for parameter 'filter' of operation 'updat
e-properties'. Current: false; legacy: true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'any' for parameter 'filter' of oper
ation 'update-properties'. Current: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'any' for parameter 'filter' of oper
ation 'update-properties'. Current: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'any' for parameter 'filter' of operation 'update-properties'. Current: f
alse; legacy: true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for parameter 'filter' of operation 'update-properties'
. Current: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for parameter 'filter' of operation 'update-properties'
. Current: false; legacy: true
Different 'nillable' for value-type key 'match' for parameter 'filter' of operation 'update-properties'. Current: false; legacy: true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'not' for value-type key 'all' for p
arameter 'filter' of operation 'update-properties'. Current: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'not' for value-type key 'all' for p
arameter 'filter' of operation 'update-properties'. Current: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'not' for value-type key 'all' for parameter 'filter' of operation 'updat
e-properties'. Current: false; legacy: true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'all' for parameter 'filter' of oper
ation 'update-properties'. Current: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'all' for parameter 'filter' of oper
ation 'update-properties'. Current: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'all' for parameter 'filter' of operation 'update-properties'. Current: f
alse; legacy: true
--- Problems for relative address to root ["custom-handler" => "*"]:
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'not' for attribute 'filter'. Curren
t: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'not' for attribute 'filter'. Curren
t: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'not' for attribute 'filter'. Current: false; legacy: true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'not' for value-type key 'any' for a
ttribute 'filter'. Current: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'not' for value-type key 'any' for a
ttribute 'filter'. Current: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'not' for value-type key 'any' for attribute 'filter'. Current: false; le
gacy: true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'any' for attribute 'filter'. Curren
t: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'any' for attribute 'filter'. Curren
t: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'any' for attribute 'filter'. Current: false; legacy: true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for attribute 'filter'. Current: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for attribute 'filter'. Current: false; legacy: true
Different 'nillable' for value-type key 'match' for attribute 'filter'. Current: false; legacy: true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'not' for value-type key 'all' for a
ttribute 'filter'. Current: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'not' for value-type key 'all' for a
ttribute 'filter'. Current: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'not' for value-type key 'all' for attribute 'filter'. Current: false; le
gacy: true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'all' for attribute 'filter'. Curren
t: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'all' for attribute 'filter'. Curren
t: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'all' for attribute 'filter'. Current: false; legacy: true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'not' for parameter 'filter' of oper
ation 'add'. Current: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'not' for parameter 'filter' of oper
ation 'add'. Current: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'not' for parameter 'filter' of operation 'add'. Current: false; legacy:
true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'not' for value-type key 'any' for p
arameter 'filter' of operation 'add'. Current: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'not' for value-type key 'any' for p
arameter 'filter' of operation 'add'. Current: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'not' for value-type key 'any' for parameter 'filter' of operation 'add'.
Current: false; legacy: true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'any' for parameter 'filter' of oper
ation 'add'. Current: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'any' for parameter 'filter' of oper
ation 'add'. Current: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'any' for parameter 'filter' of operation 'add'. Current: false; legacy:
true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for parameter 'filter' of operation 'add'. Current: fal
se; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for parameter 'filter' of operation 'add'. Current: fal
se; legacy: true
Different 'nillable' for value-type key 'match' for parameter 'filter' of operation 'add'. Current: false; legacy: true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'not' for value-type key 'all' for p
arameter 'filter' of operation 'add'. Current: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'not' for value-type key 'all' for p
arameter 'filter' of operation 'add'. Current: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'not' for value-type key 'all' for parameter 'filter' of operation 'add'.
Current: false; legacy: true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'all' for parameter 'filter' of oper
ation 'add'. Current: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'all' for parameter 'filter' of oper
ation 'add'. Current: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'all' for parameter 'filter' of operation 'add'. Current: false; legacy:
true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'not' for parameter 'filter' of oper
ation 'update-properties'. Current: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'not' for parameter 'filter' of oper
ation 'update-properties'. Current: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'not' for parameter 'filter' of operation 'update-properties'. Current: f
alse; legacy: true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'not' for value-type key 'any' for p
arameter 'filter' of operation 'update-properties'. Current: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'not' for value-type key 'any' for p
arameter 'filter' of operation 'update-properties'. Current: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'not' for value-type key 'any' for parameter 'filter' of operation 'updat
e-properties'. Current: false; legacy: true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'any' for parameter 'filter' of oper
ation 'update-properties'. Current: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'any' for parameter 'filter' of oper
ation 'update-properties'. Current: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'any' for parameter 'filter' of operation 'update-properties'. Current: f
alse; legacy: true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for parameter 'filter' of operation 'update-properties'
. Current: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for parameter 'filter' of operation 'update-properties'
. Current: false; legacy: true
Different 'nillable' for value-type key 'match' for parameter 'filter' of operation 'update-properties'. Current: false; legacy: true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'not' for value-type key 'all' for p
arameter 'filter' of operation 'update-properties'. Current: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'not' for value-type key 'all' for p
arameter 'filter' of operation 'update-properties'. Current: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'not' for value-type key 'all' for parameter 'filter' of operation 'updat
e-properties'. Current: false; legacy: true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'all' for parameter 'filter' of oper
ation 'update-properties'. Current: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'all' for parameter 'filter' of oper
ation 'update-properties'. Current: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'all' for parameter 'filter' of operation 'update-properties'. Current: f
alse; legacy: true
--- Problems for relative address to root ["file-handler" => "*"]:
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'not' for attribute 'filter'. Curren
t: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'not' for attribute 'filter'. Curren
t: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'not' for attribute 'filter'. Current: false; legacy: true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'not' for value-type key 'any' for a
ttribute 'filter'. Current: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'not' for value-type key 'any' for a
ttribute 'filter'. Current: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'not' for value-type key 'any' for attribute 'filter'. Current: false; le
gacy: true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'any' for attribute 'filter'. Curren
t: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'any' for attribute 'filter'. Curren
t: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'any' for attribute 'filter'. Current: false; legacy: true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for attribute 'filter'. Current: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for attribute 'filter'. Current: false; legacy: true
Different 'nillable' for value-type key 'match' for attribute 'filter'. Current: false; legacy: true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'not' for value-type key 'all' for a
ttribute 'filter'. Current: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'not' for value-type key 'all' for a
ttribute 'filter'. Current: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'not' for value-type key 'all' for attribute 'filter'. Current: false; le
gacy: true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'all' for attribute 'filter'. Curren
t: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'all' for attribute 'filter'. Curren
t: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'all' for attribute 'filter'. Current: false; legacy: true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'not' for parameter 'filter' of oper
ation 'add'. Current: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'not' for parameter 'filter' of oper
ation 'add'. Current: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'not' for parameter 'filter' of operation 'add'. Current: false; legacy:
true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'not' for value-type key 'any' for p
arameter 'filter' of operation 'add'. Current: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'not' for value-type key 'any' for p
arameter 'filter' of operation 'add'. Current: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'not' for value-type key 'any' for parameter 'filter' of operation 'add'.
Current: false; legacy: true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'any' for parameter 'filter' of oper
ation 'add'. Current: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'any' for parameter 'filter' of oper
ation 'add'. Current: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'any' for parameter 'filter' of operation 'add'. Current: false; legacy:
true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for parameter 'filter' of operation 'add'. Current: fal
se; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for parameter 'filter' of operation 'add'. Current: fal
se; legacy: true
Different 'nillable' for value-type key 'match' for parameter 'filter' of operation 'add'. Current: false; legacy: true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'not' for value-type key 'all' for p
arameter 'filter' of operation 'add'. Current: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'not' for value-type key 'all' for p
arameter 'filter' of operation 'add'. Current: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'not' for value-type key 'all' for parameter 'filter' of operation 'add'.
Current: false; legacy: true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'all' for parameter 'filter' of oper
ation 'add'. Current: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'all' for parameter 'filter' of oper
ation 'add'. Current: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'all' for parameter 'filter' of operation 'add'. Current: false; legacy:
true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'not' for parameter 'filter' of oper
ation 'update-properties'. Current: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'not' for parameter 'filter' of oper
ation 'update-properties'. Current: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'not' for parameter 'filter' of operation 'update-properties'. Current: f
alse; legacy: true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'not' for value-type key 'any' for p
arameter 'filter' of operation 'update-properties'. Current: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'not' for value-type key 'any' for p
arameter 'filter' of operation 'update-properties'. Current: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'not' for value-type key 'any' for parameter 'filter' of operation 'updat
e-properties'. Current: false; legacy: true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'any' for parameter 'filter' of oper
ation 'update-properties'. Current: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'any' for parameter 'filter' of oper
ation 'update-properties'. Current: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'any' for parameter 'filter' of operation 'update-properties'. Current: f
alse; legacy: true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for parameter 'filter' of operation 'update-properties'
. Current: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for parameter 'filter' of operation 'update-properties'
. Current: false; legacy: true
Different 'nillable' for value-type key 'match' for parameter 'filter' of operation 'update-properties'. Current: false; legacy: true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'not' for value-type key 'all' for p
arameter 'filter' of operation 'update-properties'. Current: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'not' for value-type key 'all' for p
arameter 'filter' of operation 'update-properties'. Current: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'not' for value-type key 'all' for parameter 'filter' of operation 'updat
e-properties'. Current: false; legacy: true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'all' for parameter 'filter' of oper
ation 'update-properties'. Current: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'all' for parameter 'filter' of oper
ation 'update-properties'. Current: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'all' for parameter 'filter' of operation 'update-properties'. Current: f
alse; legacy: true
--- Problems for relative address to root ["logger" => "*"]:
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'not' for attribute 'filter'. Curren
t: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'not' for attribute 'filter'. Curren
t: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'not' for attribute 'filter'. Current: false; legacy: true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'not' for value-type key 'any' for a
ttribute 'filter'. Current: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'not' for value-type key 'any' for a
ttribute 'filter'. Current: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'not' for value-type key 'any' for attribute 'filter'. Current: false; le
gacy: true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'any' for attribute 'filter'. Curren
t: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'any' for attribute 'filter'. Curren
t: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'any' for attribute 'filter'. Current: false; legacy: true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for attribute 'filter'. Current: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for attribute 'filter'. Current: false; legacy: true
Different 'nillable' for value-type key 'match' for attribute 'filter'. Current: false; legacy: true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'not' for value-type key 'all' for a
ttribute 'filter'. Current: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'not' for value-type key 'all' for a
ttribute 'filter'. Current: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'not' for value-type key 'all' for attribute 'filter'. Current: false; le
gacy: true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'all' for attribute 'filter'. Curren
t: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'all' for attribute 'filter'. Curren
t: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'all' for attribute 'filter'. Current: false; legacy: true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'not' for parameter 'filter' of oper
ation 'add'. Current: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'not' for parameter 'filter' of oper
ation 'add'. Current: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'not' for parameter 'filter' of operation 'add'. Current: false; legacy:
true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'not' for value-type key 'any' for p
arameter 'filter' of operation 'add'. Current: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'not' for value-type key 'any' for p
arameter 'filter' of operation 'add'. Current: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'not' for value-type key 'any' for parameter 'filter' of operation 'add'.
Current: false; legacy: true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'any' for parameter 'filter' of oper
ation 'add'. Current: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'any' for parameter 'filter' of oper
ation 'add'. Current: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'any' for parameter 'filter' of operation 'add'. Current: false; legacy:
true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for parameter 'filter' of operation 'add'. Current: fal
se; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for parameter 'filter' of operation 'add'. Current: fal
se; legacy: true
Different 'nillable' for value-type key 'match' for parameter 'filter' of operation 'add'. Current: false; legacy: true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'not' for value-type key 'all' for p
arameter 'filter' of operation 'add'. Current: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'not' for value-type key 'all' for p
arameter 'filter' of operation 'add'. Current: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'not' for value-type key 'all' for parameter 'filter' of operation 'add'.
Current: false; legacy: true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'all' for parameter 'filter' of oper
ation 'add'. Current: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'all' for parameter 'filter' of oper
ation 'add'. Current: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'all' for parameter 'filter' of operation 'add'. Current: false; legacy:
true
--- Problems for relative address to root ["logging-profile" => "*","size-rotating-file-handler" => "*"]:
Missing attributes in current: []; missing in legacy [rotate-on-boot]
Missing parameters for operation 'add' in current: []; missing in legacy [rotate-on-boot]
Missing parameters for operation 'update-properties' in current: []; missing in legacy [rotate-on-boot]
--- Problems for relative address to root ["periodic-rotating-file-handler" => "*"]:
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'not' for attribute 'filter'. Curren
t: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'not' for attribute 'filter'. Curren
t: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'not' for attribute 'filter'. Current: false; legacy: true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'not' for value-type key 'any' for a
ttribute 'filter'. Current: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'not' for value-type key 'any' for a
ttribute 'filter'. Current: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'not' for value-type key 'any' for attribute 'filter'. Current: false; le
gacy: true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'any' for attribute 'filter'. Curren
t: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'any' for attribute 'filter'. Curren
t: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'any' for attribute 'filter'. Current: false; legacy: true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for attribute 'filter'. Current: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for attribute 'filter'. Current: false; legacy: true
Different 'nillable' for value-type key 'match' for attribute 'filter'. Current: false; legacy: true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'not' for value-type key 'all' for a
ttribute 'filter'. Current: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'not' for value-type key 'all' for a
ttribute 'filter'. Current: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'not' for value-type key 'all' for attribute 'filter'. Current: false; le
gacy: true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'all' for attribute 'filter'. Curren
t: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'all' for attribute 'filter'. Curren
t: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'all' for attribute 'filter'. Current: false; legacy: true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'not' for parameter 'filter' of oper
ation 'add'. Current: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'not' for parameter 'filter' of oper
ation 'add'. Current: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'not' for parameter 'filter' of operation 'add'. Current: false; legacy:
true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'not' for value-type key 'any' for p
arameter 'filter' of operation 'add'. Current: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'not' for value-type key 'any' for p
arameter 'filter' of operation 'add'. Current: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'not' for value-type key 'any' for parameter 'filter' of operation 'add'.
Current: false; legacy: true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'any' for parameter 'filter' of oper
ation 'add'. Current: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'any' for parameter 'filter' of oper
ation 'add'. Current: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'any' for parameter 'filter' of operation 'add'. Current: false; legacy:
true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for parameter 'filter' of operation 'add'. Current: fal
se; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for parameter 'filter' of operation 'add'. Current: fal
se; legacy: true
Different 'nillable' for value-type key 'match' for parameter 'filter' of operation 'add'. Current: false; legacy: true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'not' for value-type key 'all' for p
arameter 'filter' of operation 'add'. Current: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'not' for value-type key 'all' for p
arameter 'filter' of operation 'add'. Current: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'not' for value-type key 'all' for parameter 'filter' of operation 'add'.
Current: false; legacy: true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'all' for parameter 'filter' of oper
ation 'add'. Current: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'all' for parameter 'filter' of oper
ation 'add'. Current: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'all' for parameter 'filter' of operation 'add'. Current: false; legacy:
true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'not' for parameter 'filter' of oper
ation 'update-properties'. Current: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'not' for parameter 'filter' of oper
ation 'update-properties'. Current: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'not' for parameter 'filter' of operation 'update-properties'. Current: f
alse; legacy: true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'not' for value-type key 'any' for p
arameter 'filter' of operation 'update-properties'. Current: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'not' for value-type key 'any' for p
arameter 'filter' of operation 'update-properties'. Current: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'not' for value-type key 'any' for parameter 'filter' of operation 'updat
e-properties'. Current: false; legacy: true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'any' for parameter 'filter' of oper
ation 'update-properties'. Current: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'any' for parameter 'filter' of oper
ation 'update-properties'. Current: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'any' for parameter 'filter' of operation 'update-properties'. Current: f
alse; legacy: true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for parameter 'filter' of operation 'update-properties'
. Current: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for parameter 'filter' of operation 'update-properties'
. Current: false; legacy: true
Different 'nillable' for value-type key 'match' for parameter 'filter' of operation 'update-properties'. Current: false; legacy: true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'not' for value-type key 'all' for p
arameter 'filter' of operation 'update-properties'. Current: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'not' for value-type key 'all' for p
arameter 'filter' of operation 'update-properties'. Current: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'not' for value-type key 'all' for parameter 'filter' of operation 'updat
e-properties'. Current: false; legacy: true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'all' for parameter 'filter' of oper
ation 'update-properties'. Current: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'all' for parameter 'filter' of oper
ation 'update-properties'. Current: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'all' for parameter 'filter' of operation 'update-properties'. Current: f
alse; legacy: true
--- Problems for relative address to root ["root-logger" => "ROOT"]:
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'not' for attribute 'filter'. Curren
t: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'not' for attribute 'filter'. Curren
t: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'not' for attribute 'filter'. Current: false; legacy: true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'not' for value-type key 'any' for a
ttribute 'filter'. Current: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'not' for value-type key 'any' for a
ttribute 'filter'. Current: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'not' for value-type key 'any' for attribute 'filter'. Current: false; le
gacy: true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'any' for attribute 'filter'. Curren
t: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'any' for attribute 'filter'. Curren
t: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'any' for attribute 'filter'. Current: false; legacy: true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for attribute 'filter'. Current: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for attribute 'filter'. Current: false; legacy: true
Different 'nillable' for value-type key 'match' for attribute 'filter'. Current: false; legacy: true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'not' for value-type key 'all' for a
ttribute 'filter'. Current: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'not' for value-type key 'all' for a
ttribute 'filter'. Current: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'not' for value-type key 'all' for attribute 'filter'. Current: false; le
gacy: true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'all' for attribute 'filter'. Curren
t: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'all' for attribute 'filter'. Curren
t: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'all' for attribute 'filter'. Current: false; legacy: true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'not' for parameter 'filter' of oper
ation 'add'. Current: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'not' for parameter 'filter' of oper
ation 'add'. Current: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'not' for parameter 'filter' of operation 'add'. Current: false; legacy:
true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'not' for value-type key 'any' for p
arameter 'filter' of operation 'add'. Current: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'not' for value-type key 'any' for p
arameter 'filter' of operation 'add'. Current: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'not' for value-type key 'any' for parameter 'filter' of operation 'add'.
Current: false; legacy: true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'any' for parameter 'filter' of oper
ation 'add'. Current: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'any' for parameter 'filter' of oper
ation 'add'. Current: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'any' for parameter 'filter' of operation 'add'. Current: false; legacy:
true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for parameter 'filter' of operation 'add'. Current: fal
se; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for parameter 'filter' of operation 'add'. Current: fal
se; legacy: true
Different 'nillable' for value-type key 'match' for parameter 'filter' of operation 'add'. Current: false; legacy: true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'not' for value-type key 'all' for p
arameter 'filter' of operation 'add'. Current: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'not' for value-type key 'all' for p
arameter 'filter' of operation 'add'. Current: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'not' for value-type key 'all' for parameter 'filter' of operation 'add'.
Current: false; legacy: true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'all' for parameter 'filter' of oper
ation 'add'. Current: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'all' for parameter 'filter' of oper
ation 'add'. Current: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'all' for parameter 'filter' of operation 'add'. Current: false; legacy:
true
--- Problems for relative address to root ["size-rotating-file-handler" => "*"]:
Missing attributes in current: []; missing in legacy [rotate-on-boot]
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'not' for attribute 'filter'. Curren
t: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'not' for attribute 'filter'. Curren
t: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'not' for attribute 'filter'. Current: false; legacy: true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'not' for value-type key 'any' for a
ttribute 'filter'. Current: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'not' for value-type key 'any' for a
ttribute 'filter'. Current: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'not' for value-type key 'any' for attribute 'filter'. Current: false; le
gacy: true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'any' for attribute 'filter'. Curren
t: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'any' for attribute 'filter'. Curren
t: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'any' for attribute 'filter'. Current: false; legacy: true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for attribute 'filter'. Current: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for attribute 'filter'. Current: false; legacy: true
Different 'nillable' for value-type key 'match' for attribute 'filter'. Current: false; legacy: true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'not' for value-type key 'all' for a
ttribute 'filter'. Current: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'not' for value-type key 'all' for a
ttribute 'filter'. Current: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'not' for value-type key 'all' for attribute 'filter'. Current: false; le
gacy: true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'all' for attribute 'filter'. Curren
t: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'all' for attribute 'filter'. Curren
t: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'all' for attribute 'filter'. Current: false; legacy: true
Missing parameters for operation 'add' in current: []; missing in legacy [rotate-on-boot]
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'not' for parameter 'filter' of oper
ation 'add'. Current: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'not' for parameter 'filter' of oper
ation 'add'. Current: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'not' for parameter 'filter' of operation 'add'. Current: false; legacy:
true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'not' for value-type key 'any' for p
arameter 'filter' of operation 'add'. Current: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'not' for value-type key 'any' for p
arameter 'filter' of operation 'add'. Current: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'not' for value-type key 'any' for parameter 'filter' of operation 'add'.
Current: false; legacy: true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'any' for parameter 'filter' of oper
ation 'add'. Current: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'any' for parameter 'filter' of oper
ation 'add'. Current: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'any' for parameter 'filter' of operation 'add'. Current: false; legacy:
true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for parameter 'filter' of operation 'add'. Current: fal
se; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for parameter 'filter' of operation 'add'. Current: fal
se; legacy: true
Different 'nillable' for value-type key 'match' for parameter 'filter' of operation 'add'. Current: false; legacy: true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'not' for value-type key 'all' for p
arameter 'filter' of operation 'add'. Current: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'not' for value-type key 'all' for p
arameter 'filter' of operation 'add'. Current: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'not' for value-type key 'all' for parameter 'filter' of operation 'add'.
Current: false; legacy: true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'all' for parameter 'filter' of oper
ation 'add'. Current: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'all' for parameter 'filter' of oper
ation 'add'. Current: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'all' for parameter 'filter' of operation 'add'. Current: false; legacy:
true
Missing parameters for operation 'update-properties' in current: []; missing in legacy [rotate-on-boot]
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'not' for parameter 'filter' of oper
ation 'update-properties'. Current: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'not' for parameter 'filter' of oper
ation 'update-properties'. Current: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'not' for parameter 'filter' of operation 'update-properties'. Current: f
alse; legacy: true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'not' for value-type key 'any' for p
arameter 'filter' of operation 'update-properties'. Current: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'not' for value-type key 'any' for p
arameter 'filter' of operation 'update-properties'. Current: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'not' for value-type key 'any' for parameter 'filter' of operation 'updat
e-properties'. Current: false; legacy: true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'any' for parameter 'filter' of oper
ation 'update-properties'. Current: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'any' for parameter 'filter' of oper
ation 'update-properties'. Current: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'any' for parameter 'filter' of operation 'update-properties'. Current: f
alse; legacy: true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for parameter 'filter' of operation 'update-properties'
. Current: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for parameter 'filter' of operation 'update-properties'
. Current: false; legacy: true
Different 'nillable' for value-type key 'match' for parameter 'filter' of operation 'update-properties'. Current: false; legacy: true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'not' for value-type key 'all' for p
arameter 'filter' of operation 'update-properties'. Current: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'not' for value-type key 'all' for p
arameter 'filter' of operation 'update-properties'. Current: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'not' for value-type key 'all' for parameter 'filter' of operation 'updat
e-properties'. Current: false; legacy: true
Different 'nillable' for value-type key 'max-level' for value-type key 'level-range' for value-type key 'all' for parameter 'filter' of oper
ation 'update-properties'. Current: false; legacy: true
Different 'nillable' for value-type key 'min-level' for value-type key 'level-range' for value-type key 'all' for parameter 'filter' of oper
ation 'update-properties'. Current: false; legacy: true
Different 'nillable' for value-type key 'match' for value-type key 'all' for parameter 'filter' of operation 'update-properties'. Current: f
alse; legacy: true
====== Resource root address: ["subsystem" => "mail"] - Current version: 1.3.0; legacy version: 1.2.0 =======
====== Resource root address: ["subsystem" => "messaging"] - Current version: 1.3.0; legacy version: 1.2.0 =======
--- Problems for relative address to root ["hornetq-server" => "*"]:
Missing attributes in current: []; missing in legacy [active]
Different 'storage' for attribute 'clustered'. Current: "configuration"; legacy: "runtime"
Missing parameters for operation 'add' in current: []; missing in legacy [clustered]
--- Problems for relative address to root ["hornetq-server" => "*","core-address" => "*","role" => "*"]:
Different 'default' for attribute 'consume'. Current: false; legacy: undefined
Different 'default' for attribute 'create-durable-queue'. Current: false; legacy: undefined
Different 'default' for attribute 'create-non-durable-queue'. Current: false; legacy: undefined
Different 'default' for attribute 'delete-durable-queue'. Current: false; legacy: undefined
Different 'default' for attribute 'delete-non-durable-queue'. Current: false; legacy: undefined
Different 'default' for attribute 'manage'. Current: false; legacy: undefined
Different 'default' for attribute 'send'. Current: false; legacy: undefined
--- Problems for relative address to root ["hornetq-server" => "*","jms-queue" => "*"]:
Different 'access-type' for attribute 'durable'. Current: "read-only"; legacy: "read-write"
Different 'access-type' for attribute 'entries'. Current: "read-only"; legacy: "read-write"
Different 'access-type' for attribute 'selector'. Current: "read-only"; legacy: "read-write"
--- Problems for relative address to root ["hornetq-server" => "*","queue" => "*"]:
Different 'access-type' for attribute 'durable'. Current: "read-only"; legacy: "read-write"
Different 'access-type' for attribute 'filter'. Current: "read-only"; legacy: "read-write"
Different 'access-type' for attribute 'queue-address'. Current: "read-only"; legacy: "read-write"
--- Problems for relative address to root ["hornetq-server" => "*","security-setting" => "*","role" => "*"]:
Different 'default' for attribute 'consume'. Current: false; legacy: undefined
Different 'default' for attribute 'create-durable-queue'. Current: false; legacy: undefined
Different 'default' for attribute 'create-non-durable-queue'. Current: false; legacy: undefined
Different 'default' for attribute 'delete-durable-queue'. Current: false; legacy: undefined
Different 'default' for attribute 'delete-non-durable-queue'. Current: false; legacy: undefined
Different 'default' for attribute 'manage'. Current: false; legacy: undefined
Different 'default' for attribute 'send'. Current: false; legacy: undefined
====== Resource root address: ["subsystem" => "modcluster"] - Current version: 1.4.0; legacy version: 1.3.0 =======
--- Problems for relative address to root []:
Different 'type' for 'reply-properties' for operation 'list-proxies'. Current: LIST; legacy: undefined
Different 'value-type' for 'reply-properties' for operation 'list-proxies'. Current: STRING; legacy: undefined
Different 'type' for 'reply-properties' for operation 'read-proxies-configuration'. Current: LIST; legacy: undefined
Different 'value-type' for 'reply-properties' for operation 'read-proxies-configuration'. Current: STRING; legacy: undefined
Different 'type' for 'reply-properties' for operation 'read-proxies-info'. Current: LIST; legacy: undefined
Different 'value-type' for 'reply-properties' for operation 'read-proxies-info'. Current: STRING; legacy: undefined
Missing parameters for operation 'stop' in current: []; missing in legacy [waittime]
====== Resource root address: ["subsystem" => "naming"] - Current version: 1.3.0; legacy version: 1.2.0 =======
--- Problems for relative address to root ["binding" => "*"]:
Missing attributes in current: []; missing in legacy [cache]
Missing parameters for operation 'add' in current: []; missing in legacy [cache]
====== Resource root address: ["subsystem" => "pojo"] - Current version: 1.0.0; legacy version: 1.0.0 =======
====== Resource root address: ["subsystem" => "remoting"] - Current version: 1.3.0; legacy version: 1.2.0 =======
====== Resource root address: ["subsystem" => "resource-adapters"] - Current version: 1.3.0; legacy version: 1.2.0 =======
====== Resource root address: ["subsystem" => "sar"] - Current version: 1.0.0; legacy version: 1.0.0 =======
====== Resource root address: ["subsystem" => "security"] - Current version: 1.3.0; legacy version: 1.2.0 =======
--- Problems for relative address to root ["security-domain" => "*","acl" => "classic"]:
Missing parameters for operation 'add' in current: []; missing in legacy [acl-modules]
--- Problems for relative address to root ["security-domain" => "*","audit" => "classic"]:
Missing parameters for operation 'add' in current: []; missing in legacy [provider-modules]
--- Problems for relative address to root ["security-domain" => "*","authentication" => "classic"]:
Missing parameters for operation 'add' in current: []; missing in legacy [login-modules]
--- Problems for relative address to root ["security-domain" => "*","authentication" => "jaspi"]:
Missing parameters for operation 'add' in current: []; missing in legacy [auth-modules]
--- Problems for relative address to root ["security-domain" => "*","authentication" => "jaspi","login-module-stack" => "*"]:
Missing parameters for operation 'add' in current: []; missing in legacy [login-modules]
--- Problems for relative address to root ["security-domain" => "*","authorization" => "classic"]:
Missing parameters for operation 'add' in current: []; missing in legacy [policy-modules]
--- Problems for relative address to root ["security-domain" => "*","identity-trust" => "classic"]:
Missing parameters for operation 'add' in current: []; missing in legacy [trust-modules]
--- Problems for relative address to root ["security-domain" => "*","jsse" => "classic"]:
Different 'nillable' for value-type key 'password' for attribute 'keystore'. Current: false; legacy: true
Different 'nillable' for value-type key 'password' for attribute 'truststore'. Current: false; legacy: true
Different 'nillable' for value-type key 'password' for parameter 'keystore' of operation 'add'. Current: false; legacy: true
Different 'nillable' for value-type key 'password' for parameter 'truststore' of operation 'add'. Current: false; legacy: true
--- Problems for relative address to root ["security-domain" => "*","mapping" => "classic"]:
Missing parameters for operation 'add' in current: []; missing in legacy [mapping-modules]
====== Resource root address: ["subsystem" => "threads"] - Current version: 1.1.0; legacy version: 1.1.0 =======
====== Resource root address: ["subsystem" => "transactions"] - Current version: 1.3.0; legacy version: 1.2.0 =======
--- Problems for relative address to root []:
Missing attributes in current: []; missing in legacy [hornetq-store-enable-async-io]
Missing parameters for operation 'add' in current: []; missing in legacy [hornetq-store-enable-async-io]
====== Resource root address: ["subsystem" => "web"] - Current version: 1.3.0; legacy version: 1.2.0 =======
--- Problems for relative address to root ["virtual-server" => "*","rewrite" => "*","condition" => "*"]:
Different 'nillable' for attribute 'flags'. Current: true; legacy: false
Different 'nillable' for parameter 'flags' of operation 'add'. Current: true; legacy: false
====== Resource root address: ["subsystem" => "webservices"] - Current version: 1.2.0; legacy version: 1.2.0 =======
====== Resource root address: ["subsystem" => "weld"] - Current version: 1.0.0; legacy version: 1.0.0 =======
Done comparison of STANDALONE!
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment