Skip to content

Instantly share code, notes, and snippets.

@kabir
Last active December 24, 2015 16:08
Show Gist options
  • Select an option

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

Select an option

Save kabir/6825559 to your computer and use it in GitHub Desktop.
Standalone WF8 and 7.2.0 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
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...
Nov 28, 2013 5:03:59 PM org.xnio.Xnio <clinit>
INFO: XNIO version 3.2.0.Beta3
Nov 28, 2013 5:03:59 PM org.xnio.nio.NioXnio <clinit>
INFO: XNIO NIO Implementation Version 3.2.0.Beta3
Nov 28, 2013 5:03:59 PM org.jboss.remoting3.EndpointImpl <clinit>
INFO: JBoss Remoting version (unknown)
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: 2.0.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 'deprecated' for parameter 'any-ipv4-address' of operation 'resolve-internet-address'. Current: {
"since" => "2.0.0",
"reason" => "Use any-address"
}; legacy: undefined
Different 'deprecated' for parameter 'any-ipv6-address' of operation 'resolve-internet-address'. Current: {
"since" => "2.0.0",
"reason" => "Use any-address"
}; legacy: undefined
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","ldap-connection" => "*"]:
Missing child types in current: []; missing in legacy [property]
--- Problems for relative address to root ["core-service" => "management","management-interface" => "http-interface"]:
Missing attributes in current: []; missing in legacy [http-upgrade-enabled]
Missing parameters for operation 'add' in current: []; missing in legacy [http-upgrade-enabled]
--- 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" => "*"]:
Missing child names for type=subsystem in current: [web]; missing in legacy [undertow]
--- Problems for relative address to root ["deployment" => "*","subdeployment" => "*","subsystem" => "datasources","data-source" => "*"]:
Missing attributes in current: []; missing in legacy [capacity-decrementer-properties, capacity-decrementer-class, capacity-incrementer-clas
s, connection-listener-class, connection-properties, capacity-incrementer-properties, initial-pool-size, connection-listener-property]
Different 'storage' for attribute 'enabled'. Current: "runtime"; legacy: "configuration"
Different 'alternatives' for attribute 'security-domain'. Current: ["user-name"]; legacy: undefined
Different 'alternatives' for attribute 'user-name'. Current: ["security-domain"]; legacy: undefined
Missing operations in current: []; missing in legacy [flush-gracefully-connection-in-pool, flush-invalid-connection-in-pool]
Missing parameters for operation 'test-connection-in-pool' in current: []; missing in legacy [user-name, password]
--- Problems for relative address to root ["deployment" => "*","subdeployment" => "*","subsystem" => "datasources","data-source" => "*","con
nection-properties" => "*"]:
Different 'nillable' for attribute 'value'. Current: true; legacy: false
--- Problems for relative address to root ["deployment" => "*","subdeployment" => "*","subsystem" => "datasources","xa-data-source" => "*"]:
Missing attributes in current: [jta]; missing in legacy [capacity-decrementer-properties, capacity-decrementer-class, capacity-incrementer-c
lass, connection-listener-class, capacity-incrementer-properties, url-property, initial-pool-size, connection-listener-property]
Different 'storage' for attribute 'enabled'. Current: "runtime"; legacy: "configuration"
Different 'alternatives' for attribute 'recovery-security-domain'. Current: ["recovery-username"]; legacy: undefined
Different 'alternatives' for attribute 'recovery-username'. Current: ["recovery-security-domain"]; legacy: undefined
Different 'alternatives' for attribute 'security-domain'. Current: ["user-name"]; legacy: undefined
Different 'alternatives' for attribute 'user-name'. Current: ["security-domain"]; legacy: undefined
Missing operations in current: []; missing in legacy [flush-gracefully-connection-in-pool, flush-invalid-connection-in-pool]
Missing parameters for operation 'test-connection-in-pool' in current: []; missing in legacy [user-name, password]
--- Problems for relative address to root ["deployment" => "*","subdeployment" => "*","subsystem" => "ejb3","entity-bean" => "*"]:
Missing attributes in current: []; missing in legacy [methods]
Missing child types in current: []; missing in legacy [service]
--- 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]
Missing child types in current: []; missing in legacy [service]
--- Problems for relative address to root ["deployment" => "*","subdeployment" => "*","subsystem" => "ejb3","singleton-bean" => "*"]:
Missing attributes in current: []; missing in legacy [methods]
Missing child types in current: []; missing in legacy [service]
--- 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]
Missing child types in current: []; missing in legacy [service]
--- Problems for relative address to root ["deployment" => "*","subdeployment" => "*","subsystem" => "ejb3","stateless-session-bean" => "*"]
:
Missing attributes in current: []; missing in legacy [methods]
Missing child types in current: []; missing in legacy [service]
--- Problems for relative address to root ["deployment" => "*","subdeployment" => "*","subsystem" => "jpa"]:
Missing child types in current: [hibernate-persistence-unit]; missing in legacy []
--- 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]
Missing child types in current: []; missing in legacy [pooled-connection-factory]
--- Problems for relative address to root ["deployment" => "*","subdeployment" => "*","subsystem" => "webservices","endpoint" => "*"]:
Missing attributes in current: []; missing in legacy [class, type, wsdl-url, name, context]
--- Problems for relative address to root ["deployment" => "*"]:
Missing child names for type=subsystem in current: [web]; missing in legacy [undertow]
--- Problems for relative address to root ["deployment" => "*","subsystem" => "datasources","data-source" => "*"]:
Missing attributes in current: []; missing in legacy [capacity-decrementer-properties, capacity-decrementer-class, capacity-incrementer-clas
s, connection-listener-class, connection-properties, capacity-incrementer-properties, initial-pool-size, connection-listener-property]
Different 'storage' for attribute 'enabled'. Current: "runtime"; legacy: "configuration"
Different 'alternatives' for attribute 'security-domain'. Current: ["user-name"]; legacy: undefined
Different 'alternatives' for attribute 'user-name'. Current: ["security-domain"]; legacy: undefined
Missing operations in current: []; missing in legacy [flush-gracefully-connection-in-pool, flush-invalid-connection-in-pool]
Missing parameters for operation 'test-connection-in-pool' in current: []; missing in legacy [user-name, password]
--- Problems for relative address to root ["deployment" => "*","subsystem" => "datasources","data-source" => "*","connection-properties" =>
"*"]:
Different 'nillable' for attribute 'value'. Current: true; legacy: false
--- Problems for relative address to root ["deployment" => "*","subsystem" => "datasources","xa-data-source" => "*"]:
Missing attributes in current: [jta]; missing in legacy [capacity-decrementer-properties, capacity-decrementer-class, capacity-incrementer-c
lass, connection-listener-class, capacity-incrementer-properties, url-property, initial-pool-size, connection-listener-property]
Different 'storage' for attribute 'enabled'. Current: "runtime"; legacy: "configuration"
Different 'alternatives' for attribute 'recovery-security-domain'. Current: ["recovery-username"]; legacy: undefined
Different 'alternatives' for attribute 'recovery-username'. Current: ["recovery-security-domain"]; legacy: undefined
Different 'alternatives' for attribute 'security-domain'. Current: ["user-name"]; legacy: undefined
Different 'alternatives' for attribute 'user-name'. Current: ["security-domain"]; legacy: undefined
Missing operations in current: []; missing in legacy [flush-gracefully-connection-in-pool, flush-invalid-connection-in-pool]
Missing parameters for operation 'test-connection-in-pool' in current: []; missing in legacy [user-name, password]
--- Problems for relative address to root ["deployment" => "*","subsystem" => "ejb3","entity-bean" => "*"]:
Missing attributes in current: []; missing in legacy [methods]
Missing child types in current: []; missing in legacy [service]
--- 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]
Missing child types in current: []; missing in legacy [service]
--- Problems for relative address to root ["deployment" => "*","subsystem" => "ejb3","singleton-bean" => "*"]:
Missing attributes in current: []; missing in legacy [methods]
Missing child types in current: []; missing in legacy [service]
--- 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]
Missing child types in current: []; missing in legacy [service]
--- Problems for relative address to root ["deployment" => "*","subsystem" => "ejb3","stateless-session-bean" => "*"]:
Missing attributes in current: []; missing in legacy [methods]
Missing child types in current: []; missing in legacy [service]
--- Problems for relative address to root ["deployment" => "*","subsystem" => "jpa"]:
Missing child types in current: [hibernate-persistence-unit]; missing in legacy []
--- 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]
Missing child types in current: []; missing in legacy [pooled-connection-factory]
--- Problems for relative address to root ["deployment" => "*","subsystem" => "webservices","endpoint" => "*"]:
Missing attributes in current: []; missing in legacy [class, type, wsdl-url, name, context]
--- Problems for relative address to root ["interface" => "*"]:
Different 'deprecated' for attribute 'any-ipv4-address'. Current: {
"since" => "2.0.0",
"reason" => "In the absence of -Djava.net.preferIPv4Stack=true, the JVM cannot be instructed to bind a socket to all IPv4 addresses, but
only to IPv4 addresses, so the intended semantic cannot be obtained via this setting alone. Since using any-address and setting -Djava.net.
preferIPv4Stack=true provides the same effect, this any-ipv4-address attribute will be removed in a future release"
}; legacy: undefined
Different 'deprecated' for attribute 'any-ipv6-address'. Current: {
"since" => "2.0.0",
"reason" => "The name of this attribute implies sockets will be reachable only via IPv6 addresses and not via IPv4, but this is not the
case. Since using any-address provides the same effect, this any-ipv6-address will be removed in a future release."
}; legacy: undefined
Different 'deprecated' for parameter 'any-ipv4-address' of operation 'add'. Current: {
"since" => "2.0.0",
"reason" => "In the absence of -Djava.net.preferIPv4Stack=true, the JVM cannot be instructed to bind a socket to all IPv4 addresses, but
only to IPv4 addresses, so the intended semantic cannot be obtained via this setting alone. Since using any-address and setting -Djava.net.
preferIPv4Stack=true provides the same effect, this any-ipv4-address attribute will be removed in a future release"
}; legacy: undefined
Different 'deprecated' for parameter 'any-ipv6-address' of operation 'add'. Current: {
"since" => "2.0.0",
"reason" => "The name of this attribute implies sockets will be reachable only via IPv6 addresses and not via IPv4, but this is not the
case. Since using any-address provides the same effect, this any-ipv6-address will be removed in a future release."
}; legacy: undefined
Different 'deprecated' for parameter 'any-ipv4-address' of operation 'resolve-internet-address'. Current: {
"since" => "2.0.0",
"reason" => "Use any-address"
}; legacy: undefined
Different 'deprecated' for parameter 'any-ipv6-address' of operation 'resolve-internet-address'. Current: {
"since" => "2.0.0",
"reason" => "Use any-address"
}; legacy: undefined
====== Comparing subsystem models ======
--- Problems for relative address to root []:
Missing subsystems in current: [cmp, web, jaxr]; missing in legacy [undertow, io, batch]
====== Resource root address: ["subsystem" => "datasources"] - Current version: 2.0.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" => "*"]:
Missing attributes in current: []; missing in legacy [capacity-decrementer-properties, capacity-decrementer-class, capacity-incrementer-clas
s, connection-listener-class, connection-properties, capacity-incrementer-properties, initial-pool-size, connection-listener-property]
Different 'access-type' for attribute 'enabled'. Current: "read-write"; legacy: "read-only"
Different 'alternatives' for attribute 'security-domain'. Current: ["user-name"]; legacy: undefined
Different 'alternatives' for attribute 'user-name'. Current: ["security-domain"]; legacy: undefined
Missing operations in current: []; missing in legacy [flush-gracefully-connection-in-pool, flush-invalid-connection-in-pool]
Missing parameters for operation 'add' in current: []; missing in legacy [capacity-decrementer-properties, capacity-decrementer-class, capac
ity-incrementer-class, connection-listener-class, connection-properties, capacity-incrementer-properties, initial-pool-size, connection-list
ener-property]
Different 'alternatives' for parameter 'security-domain' of operation 'add'. Current: ["user-name"]; legacy: undefined
Different 'alternatives' for parameter 'user-name' of operation 'add'. Current: ["security-domain"]; legacy: undefined
Missing parameters for operation 'enable' in current: [persistent]; missing in legacy []
Missing parameters for operation 'test-connection-in-pool' in current: []; missing in legacy [user-name, password]
--- Problems for relative address to root ["data-source" => "*","connection-properties" => "*"]:
Different 'nillable' for attribute 'value'. Current: true; legacy: false
Different 'nillable' for parameter 'value' of operation 'add'. Current: true; legacy: false
--- Problems for relative address to root ["data-source" => "ExampleDS"]:
Missing attributes in current: [statistics]; missing in legacy [capacity-decrementer-properties, capacity-decrementer-class, capacity-increm
enter-class, connection-listener-class, connection-properties, capacity-incrementer-properties, initial-pool-size, connection-listener-prope
rty]
Different 'access-type' for attribute 'enabled'. Current: "read-write"; legacy: "read-only"
Different 'alternatives' for attribute 'security-domain'. Current: ["user-name"]; legacy: undefined
Different 'alternatives' for attribute 'user-name'. Current: ["security-domain"]; legacy: undefined
Missing operations in current: []; missing in legacy [flush-gracefully-connection-in-pool, flush-invalid-connection-in-pool]
Missing parameters for operation 'add' in current: []; missing in legacy [capacity-decrementer-properties, capacity-decrementer-class, capac
ity-incrementer-class, connection-listener-class, connection-properties, capacity-incrementer-properties, initial-pool-size, connection-list
ener-property]
Different 'alternatives' for parameter 'security-domain' of operation 'add'. Current: ["user-name"]; legacy: undefined
Different 'alternatives' for parameter 'user-name' of operation 'add'. Current: ["security-domain"]; legacy: undefined
Missing parameters for operation 'enable' in current: [persistent]; missing in legacy []
Missing parameters for operation 'test-connection-in-pool' in current: []; missing in legacy [user-name, password]
--- Problems for relative address to root ["data-source" => "ExampleDS","connection-properties" => "*"]:
Different 'nillable' for attribute 'value'. Current: true; legacy: false
Different 'nillable' for parameter 'value' of operation 'add'. Current: true; legacy: false
--- Problems for relative address to root ["data-source" => "ExampleDS","statistics" => "pool"]:
Missing attributes in current: []; missing in legacy [BlockingFailureCount, TotalGetTime, IdleCount, AverageGetTime, WaitCount, MaxGetTime]
--- Problems for relative address to root ["xa-data-source" => "*"]:
Missing attributes in current: [jta]; missing in legacy [capacity-decrementer-properties, capacity-decrementer-class, capacity-incrementer-c
lass, connection-listener-class, capacity-incrementer-properties, url-property, initial-pool-size, connection-listener-property]
Different 'access-type' for attribute 'enabled'. Current: "read-write"; legacy: "read-only"
Different 'alternatives' for attribute 'recovery-security-domain'. Current: ["recovery-username"]; legacy: undefined
Different 'alternatives' for attribute 'recovery-username'. Current: ["recovery-security-domain"]; legacy: undefined
Different 'alternatives' for attribute 'security-domain'. Current: ["user-name"]; legacy: undefined
Different 'alternatives' for attribute 'user-name'. Current: ["security-domain"]; legacy: undefined
Missing operations in current: []; missing in legacy [flush-gracefully-connection-in-pool, flush-invalid-connection-in-pool]
Missing parameters for operation 'add' in current: [jta]; missing in legacy [capacity-decrementer-properties, capacity-decrementer-class, ca
pacity-incrementer-class, connection-listener-class, capacity-incrementer-properties, url-property, initial-pool-size, connection-listener-p
roperty]
Different 'alternatives' for parameter 'recovery-security-domain' of operation 'add'. Current: ["recovery-username"]; legacy: undefined
Different 'alternatives' for parameter 'recovery-username' of operation 'add'. Current: ["recovery-security-domain"]; legacy: undefined
Different 'alternatives' for parameter 'security-domain' of operation 'add'. Current: ["user-name"]; legacy: undefined
Different 'alternatives' for parameter 'user-name' of operation 'add'. Current: ["security-domain"]; legacy: undefined
Missing parameters for operation 'enable' in current: [persistent]; missing in legacy []
Missing parameters for operation 'test-connection-in-pool' in current: []; missing in legacy [user-name, password]
====== Resource root address: ["subsystem" => "deployment-scanner"] - Current version: 2.0.0; legacy version: 1.0.0 =======
--- Problems for relative address to root ["scanner" => "*"]:
Missing attributes in current: []; missing in legacy [runtime-failure-causes-rollback]
Missing parameters for operation 'add' in current: []; missing in legacy [runtime-failure-causes-rollback]
====== Resource root address: ["subsystem" => "ee"] - Current version: 2.0.0; legacy version: 1.0.0 =======
--- Problems for relative address to root []:
Missing attributes in current: []; missing in legacy [ejb-annotation-property-replacement]
Missing value-type for attribute 'global-modules' in current: []; missing in legacy [services, annotations, meta-inf]
Missing parameters for operation 'add' in current: []; missing in legacy [ejb-annotation-property-replacement]
Missing value-type for parameter 'global-modules' of operation 'add' in current: []; missing in legacy [services, annotations, meta-inf]
Missing child types in current: []; missing in legacy [managed-executor-service, context-service, service, managed-thread-factory, managed-s
cheduled-executor-service]
====== Resource root address: ["subsystem" => "ejb3"] - Current version: 2.0.0; legacy version: 1.2.0 =======
--- Problems for relative address to root []:
Missing attributes in current: []; missing in legacy [disable-default-ejb-permissions, default-sfsb-passivation-disabled-cache]
Missing parameters for operation 'add' in current: []; missing in legacy [disable-default-ejb-permissions, default-sfsb-passivation-disabled
-cache]
Missing child types in current: []; missing in legacy [passivation-store]
--- Problems for relative address to root ["cluster-passivation-store" => "*"]:
Different 'deprecated' for attribute 'client-mappings-cache'. Current: {
"since" => "2.0.0",
"reason" => "This is no longer configurable and will be ignored"
}; legacy: undefined
Different 'default' for attribute 'idle-timeout'. Current: 300; legacy: 300L
Different 'deprecated' for attribute 'idle-timeout-unit'. Current: {
"since" => "2.0.0",
"reason" => "SFSBs are no longer passivated eagerly, but only lazily as required by max-size"
}; legacy: undefined
Different 'deprecated' for attribute 'passivate-events-on-replicate'. Current: {
"since" => "2.0.0",
"reason" => "This is no longer configurable and will be ignored"
}; legacy: undefined
Different 'deprecated' for parameter 'client-mappings-cache' of operation 'add'. Current: {
"since" => "2.0.0",
"reason" => "This is no longer configurable and will be ignored"
}; legacy: undefined
Different 'deprecated' for parameter 'idle-timeout-unit' of operation 'add'. Current: {
"since" => "2.0.0",
"reason" => "SFSBs are no longer passivated eagerly, but only lazily as required by max-size"
}; legacy: undefined
Different 'deprecated' for parameter 'passivate-events-on-replicate' of operation 'add'. Current: {
"since" => "2.0.0",
"reason" => "This is no longer configurable and will be ignored"
}; legacy: undefined
--- Problems for relative address to root ["file-passivation-store" => "*"]:
Different 'deprecated' for attribute 'groups-path'. Current: {
"since" => "2.0.0",
"reason" => "Beans and bean groups are no longer stored in distinct directories"
}; legacy: undefined
Different 'default' for attribute 'idle-timeout'. Current: 300; legacy: 300L
Different 'deprecated' for attribute 'idle-timeout-unit'. Current: {
"since" => "2.0.0",
"reason" => "SFSBs are no longer passivated eagerly, but only lazily as required by max-size"
}; legacy: undefined
Different 'deprecated' for attribute 'relative-to'. Current: {
"since" => "2.0.0",
"reason" => "Use the relative-to attribute of the file-store of the relevant infinispan cache instead"
}; legacy: undefined
Different 'deprecated' for attribute 'sessions-path'. Current: {
"since" => "2.0.0",
"reason" => "Beans and bean groups are no longer stored in distinct directories"
}; legacy: undefined
Different 'deprecated' for attribute 'subdirectory-count'. Current: {
"since" => "2.0.0",
"reason" => "This is no longer configurable and will be ignored"
}; legacy: undefined
Different 'deprecated' for parameter 'groups-path' of operation 'add'. Current: {
"since" => "2.0.0",
"reason" => "Beans and bean groups are no longer stored in distinct directories"
}; legacy: undefined
Different 'deprecated' for parameter 'idle-timeout-unit' of operation 'add'. Current: {
"since" => "2.0.0",
"reason" => "SFSBs are no longer passivated eagerly, but only lazily as required by max-size"
}; legacy: undefined
Different 'deprecated' for parameter 'relative-to' of operation 'add'. Current: {
"since" => "2.0.0",
"reason" => "Use the relative-to attribute of the file-store of the relevant infinispan cache instead"
}; legacy: undefined
Different 'deprecated' for parameter 'sessions-path' of operation 'add'. Current: {
"since" => "2.0.0",
"reason" => "Beans and bean groups are no longer stored in distinct directories"
}; legacy: undefined
Different 'deprecated' for parameter 'subdirectory-count' of operation 'add'. Current: {
"since" => "2.0.0",
"reason" => "This is no longer configurable and will be ignored"
}; legacy: undefined
--- Problems for relative address to root ["service" => "timer-service"]:
Missing attributes in current: [relative-to, path]; missing in legacy [default-data-store]
Missing operations in current: [resolve-path]; missing in legacy []
Missing parameters for operation 'add' in current: [relative-to, path]; missing in legacy [default-data-store]
Missing child types in current: []; missing in legacy [file-data-store, database-data-store]
====== Resource root address: ["subsystem" => "infinispan"] - Current version: 2.0.0; legacy version: 1.4.0 =======
--- Problems for relative address to root ["cache-container" => "*"]:
Missing attributes in current: []; missing in legacy [cache-manager-status, local-address, coordinator-address, cluster-name, statistics, is
-coordinator]
Missing parameters for operation 'add' in current: []; missing in legacy [statistics]
--- Problems for relative address to root ["cache-container" => "*","distributed-cache" => "*"]:
Missing attributes in current: []; missing in legacy [cache-status, hit-ratio, remove-misses, passivations, misses, statistics, number-of-en
tries, time-since-reset, remove-hits, read-write-ratio, elapsed-time, replication-count, success-ratio, average-read-time, invalidations, re
plication-failures, hits, average-write-time, stores, average-replication-time]
Different 'alternatives' for attribute 'segments'. Current: ["virtual-nodes"]; legacy: undefined
Different 'alternatives' for attribute 'virtual-nodes'. Current: ["segments"]; legacy: undefined
Missing parameters for operation 'add' in current: []; missing in legacy [statistics]
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
Missing child types in current: []; missing in legacy [backup-for, backup]
--- Problems for relative address to root ["cache-container" => "*","distributed-cache" => "*","binary-keyed-jdbc-store" => "BINARY_KEYED_JD
BC_STORE"]:
Missing attributes in current: []; missing in legacy [cache-loader-loads, cache-loader-misses]
--- Problems for relative address to root ["cache-container" => "*","distributed-cache" => "*","eviction" => "EVICTION"]:
Missing attributes in current: []; missing in legacy [evictions]
--- Problems for relative address to root ["cache-container" => "*","distributed-cache" => "*","file-store" => "FILE_STORE"]:
Missing attributes in current: []; missing in legacy [cache-loader-loads, cache-loader-misses]
--- Problems for relative address to root ["cache-container" => "*","distributed-cache" => "*","locking" => "LOCKING"]:
Missing attributes in current: []; missing in legacy [current-concurrency-level, number-of-locks-available, number-of-locks-held]
--- Problems for relative address to root ["cache-container" => "*","distributed-cache" => "*","mixed-keyed-jdbc-store" => "MIXED_KEYED_JDBC
_STORE"]:
Missing attributes in current: []; missing in legacy [cache-loader-loads, cache-loader-misses]
--- Problems for relative address to root ["cache-container" => "*","distributed-cache" => "*","remote-store" => "REMOTE_STORE"]:
Missing attributes in current: []; missing in legacy [cache-loader-loads, cache-loader-misses]
--- Problems for relative address to root ["cache-container" => "*","distributed-cache" => "*","store" => "STORE"]:
Missing attributes in current: []; missing in legacy [cache-loader-loads, cache-loader-misses]
--- Problems for relative address to root ["cache-container" => "*","distributed-cache" => "*","string-keyed-jdbc-store" => "STRING_KEYED_JD
BC_STORE"]:
Missing attributes in current: []; missing in legacy [cache-loader-loads, cache-loader-misses]
--- Problems for relative address to root ["cache-container" => "*","distributed-cache" => "*","transaction" => "TRANSACTION"]:
Missing attributes in current: []; missing in legacy [rollbacks, commits, prepares]
Different 'default' for attribute 'locking'. Current: "PESSIMISTIC"; legacy: "OPTIMISTIC"
--- Problems for relative address to root ["cache-container" => "*","invalidation-cache" => "*"]:
Missing attributes in current: []; missing in legacy [cache-status, hit-ratio, remove-misses, passivations, misses, statistics, number-of-en
tries, time-since-reset, remove-hits, read-write-ratio, elapsed-time, replication-count, success-ratio, average-read-time, invalidations, re
plication-failures, hits, average-write-time, stores, average-replication-time]
Missing parameters for operation 'add' in current: []; missing in legacy [statistics]
--- Problems for relative address to root ["cache-container" => "*","invalidation-cache" => "*","binary-keyed-jdbc-store" => "BINARY_KEYED_J
DBC_STORE"]:
Missing attributes in current: []; missing in legacy [cache-loader-loads, cache-loader-misses]
--- Problems for relative address to root ["cache-container" => "*","invalidation-cache" => "*","eviction" => "EVICTION"]:
Missing attributes in current: []; missing in legacy [evictions]
--- Problems for relative address to root ["cache-container" => "*","invalidation-cache" => "*","file-store" => "FILE_STORE"]:
Missing attributes in current: []; missing in legacy [cache-loader-loads, cache-loader-misses]
--- Problems for relative address to root ["cache-container" => "*","invalidation-cache" => "*","locking" => "LOCKING"]:
Missing attributes in current: []; missing in legacy [current-concurrency-level, number-of-locks-available, number-of-locks-held]
--- Problems for relative address to root ["cache-container" => "*","invalidation-cache" => "*","mixed-keyed-jdbc-store" => "MIXED_KEYED_JDB
C_STORE"]:
Missing attributes in current: []; missing in legacy [cache-loader-loads, cache-loader-misses]
--- Problems for relative address to root ["cache-container" => "*","invalidation-cache" => "*","remote-store" => "REMOTE_STORE"]:
Missing attributes in current: []; missing in legacy [cache-loader-loads, cache-loader-misses]
--- Problems for relative address to root ["cache-container" => "*","invalidation-cache" => "*","store" => "STORE"]:
Missing attributes in current: []; missing in legacy [cache-loader-loads, cache-loader-misses]
--- Problems for relative address to root ["cache-container" => "*","invalidation-cache" => "*","string-keyed-jdbc-store" => "STRING_KEYED_J
DBC_STORE"]:
Missing attributes in current: []; missing in legacy [cache-loader-loads, cache-loader-misses]
--- Problems for relative address to root ["cache-container" => "*","invalidation-cache" => "*","transaction" => "TRANSACTION"]:
Missing attributes in current: []; missing in legacy [rollbacks, commits, prepares]
Different 'default' for attribute 'locking'. Current: "PESSIMISTIC"; legacy: "OPTIMISTIC"
--- Problems for relative address to root ["cache-container" => "*","local-cache" => "*"]:
Missing attributes in current: []; missing in legacy [cache-status, average-read-time, invalidations, hit-ratio, remove-misses, passivations
, misses, statistics, hits, number-of-entries, average-write-time, time-since-reset, remove-hits, read-write-ratio, elapsed-time, stores]
Missing parameters for operation 'add' in current: []; missing in legacy [statistics]
--- Problems for relative address to root ["cache-container" => "*","local-cache" => "*","binary-keyed-jdbc-store" => "BINARY_KEYED_JDBC_STO
RE"]:
Missing attributes in current: []; missing in legacy [cache-loader-loads, cache-loader-misses]
--- Problems for relative address to root ["cache-container" => "*","local-cache" => "*","eviction" => "EVICTION"]:
Missing attributes in current: []; missing in legacy [evictions]
--- Problems for relative address to root ["cache-container" => "*","local-cache" => "*","file-store" => "FILE_STORE"]:
Missing attributes in current: []; missing in legacy [cache-loader-loads, cache-loader-misses]
--- Problems for relative address to root ["cache-container" => "*","local-cache" => "*","locking" => "LOCKING"]:
Missing attributes in current: []; missing in legacy [current-concurrency-level, number-of-locks-available, number-of-locks-held]
--- Problems for relative address to root ["cache-container" => "*","local-cache" => "*","mixed-keyed-jdbc-store" => "MIXED_KEYED_JDBC_STORE
"]:
Missing attributes in current: []; missing in legacy [cache-loader-loads, cache-loader-misses]
--- Problems for relative address to root ["cache-container" => "*","local-cache" => "*","remote-store" => "REMOTE_STORE"]:
Missing attributes in current: []; missing in legacy [cache-loader-loads, cache-loader-misses]
--- Problems for relative address to root ["cache-container" => "*","local-cache" => "*","store" => "STORE"]:
Missing attributes in current: []; missing in legacy [cache-loader-loads, cache-loader-misses]
--- Problems for relative address to root ["cache-container" => "*","local-cache" => "*","string-keyed-jdbc-store" => "STRING_KEYED_JDBC_STO
RE"]:
Missing attributes in current: []; missing in legacy [cache-loader-loads, cache-loader-misses]
--- Problems for relative address to root ["cache-container" => "*","local-cache" => "*","transaction" => "TRANSACTION"]:
Missing attributes in current: []; missing in legacy [rollbacks, commits, prepares]
Different 'default' for attribute 'locking'. Current: "PESSIMISTIC"; legacy: "OPTIMISTIC"
--- Problems for relative address to root ["cache-container" => "*","replicated-cache" => "*"]:
Missing attributes in current: []; missing in legacy [cache-status, hit-ratio, remove-misses, passivations, misses, statistics, number-of-en
tries, time-since-reset, remove-hits, read-write-ratio, elapsed-time, replication-count, success-ratio, average-read-time, invalidations, re
plication-failures, hits, average-write-time, stores, average-replication-time]
Missing parameters for operation 'add' in current: []; missing in legacy [statistics]
Missing child types in current: []; missing in legacy [backup-for, backup]
--- Problems for relative address to root ["cache-container" => "*","replicated-cache" => "*","binary-keyed-jdbc-store" => "BINARY_KEYED_JDB
C_STORE"]:
Missing attributes in current: []; missing in legacy [cache-loader-loads, cache-loader-misses]
--- Problems for relative address to root ["cache-container" => "*","replicated-cache" => "*","eviction" => "EVICTION"]:
Missing attributes in current: []; missing in legacy [evictions]
--- Problems for relative address to root ["cache-container" => "*","replicated-cache" => "*","file-store" => "FILE_STORE"]:
Missing attributes in current: []; missing in legacy [cache-loader-loads, cache-loader-misses]
--- Problems for relative address to root ["cache-container" => "*","replicated-cache" => "*","locking" => "LOCKING"]:
Missing attributes in current: []; missing in legacy [current-concurrency-level, number-of-locks-available, number-of-locks-held]
--- Problems for relative address to root ["cache-container" => "*","replicated-cache" => "*","mixed-keyed-jdbc-store" => "MIXED_KEYED_JDBC_
STORE"]:
Missing attributes in current: []; missing in legacy [cache-loader-loads, cache-loader-misses]
--- Problems for relative address to root ["cache-container" => "*","replicated-cache" => "*","remote-store" => "REMOTE_STORE"]:
Missing attributes in current: []; missing in legacy [cache-loader-loads, cache-loader-misses]
--- Problems for relative address to root ["cache-container" => "*","replicated-cache" => "*","store" => "STORE"]:
Missing attributes in current: []; missing in legacy [cache-loader-loads, cache-loader-misses]
--- Problems for relative address to root ["cache-container" => "*","replicated-cache" => "*","string-keyed-jdbc-store" => "STRING_KEYED_JDB
C_STORE"]:
Missing attributes in current: []; missing in legacy [cache-loader-loads, cache-loader-misses]
--- Problems for relative address to root ["cache-container" => "*","replicated-cache" => "*","transaction" => "TRANSACTION"]:
Missing attributes in current: []; missing in legacy [rollbacks, commits, prepares]
Different 'default' for attribute 'locking'. Current: "PESSIMISTIC"; legacy: "OPTIMISTIC"
====== Resource root address: ["subsystem" => "jacorb"] - Current version: 1.3.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: 2.0.0; legacy version: 1.2.0 =======
--- Problems for relative address to root []:
Missing child types in current: []; missing in legacy [distributed-workmanager]
--- Problems for relative address to root ["bootstrap-context" => "*"]:
Different 'access-type' for attribute 'name'. Current: "read-only"; legacy: "read-write"
--- Problems for relative address to root ["cached-connection-manager" => "cached-connection-manager"]:
Missing attributes in current: []; missing in legacy [ignore-unknown-connections]
Missing operations in current: []; missing in legacy [get-number-of-connections, list-connections]
Missing parameters for operation 'add' in current: []; missing in legacy [ignore-unknown-connections]
--- Problems for relative address to root ["workmanager" => "*"]:
Different 'access-type' for attribute 'name'. Current: "read-only"; legacy: "read-write"
====== Resource root address: ["subsystem" => "jdr"] - Current version: 1.2.0; legacy version: 1.1.0 =======
====== Resource root address: ["subsystem" => "jgroups"] - Current version: 2.0.0; legacy version: 1.2.0 =======
--- Problems for relative address to root []:
Missing child types in current: []; missing in legacy [channel]
--- Problems for relative address to root ["stack" => "*"]:
Missing child types in current: []; missing in legacy [relay]
====== Resource root address: ["subsystem" => "jmx"] - Current version: 1.2.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: 2.0.0; legacy version: 1.2.0 =======
--- Problems for relative address to root []:
Missing operations in current: []; missing in legacy [read-log-file, list-log-files]
Missing child types in current: []; missing in legacy [pattern-formatter, custom-formatter]
--- 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 'alternatives' for attribute 'formatter'. Current: ["named-formatter"]; legacy: undefined
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 'alternatives' for parameter 'formatter' of operation 'add'. Current: ["named-formatter"]; legacy: undefined
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
Different 'alternatives' for parameter 'formatter' of operation 'update-properties'. Current: ["named-formatter"]; legacy: undefined
--- Problems for relative address to root ["console-handler" => "*"]:
Missing attributes in current: []; missing in legacy [named-formatter]
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 'alternatives' for attribute 'formatter'. Current: ["named-formatter"]; legacy: undefined
Missing parameters for operation 'add' in current: []; missing in legacy [named-formatter]
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 'alternatives' for parameter 'formatter' of operation 'add'. Current: ["named-formatter"]; legacy: undefined
Missing parameters for operation 'update-properties' in current: []; missing in legacy [named-formatter]
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
Different 'alternatives' for parameter 'formatter' of operation 'update-properties'. Current: ["named-formatter"]; legacy: undefined
--- Problems for relative address to root ["custom-handler" => "*"]:
Missing attributes in current: []; missing in legacy [named-formatter]
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 'alternatives' for attribute 'formatter'. Current: ["named-formatter"]; legacy: undefined
Missing parameters for operation 'add' in current: []; missing in legacy [named-formatter]
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 'alternatives' for parameter 'formatter' of operation 'add'. Current: ["named-formatter"]; legacy: undefined
Missing parameters for operation 'update-properties' in current: []; missing in legacy [named-formatter]
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
Different 'alternatives' for parameter 'formatter' of operation 'update-properties'. Current: ["named-formatter"]; legacy: undefined
--- Problems for relative address to root ["file-handler" => "*"]:
Missing attributes in current: []; missing in legacy [named-formatter]
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 'alternatives' for attribute 'formatter'. Current: ["named-formatter"]; legacy: undefined
Missing parameters for operation 'add' in current: []; missing in legacy [named-formatter]
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 'alternatives' for parameter 'formatter' of operation 'add'. Current: ["named-formatter"]; legacy: undefined
Missing parameters for operation 'update-properties' in current: []; missing in legacy [named-formatter]
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
Different 'alternatives' for parameter 'formatter' of operation 'update-properties'. Current: ["named-formatter"]; legacy: undefined
--- 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" => "*"]:
Missing child types in current: []; missing in legacy [pattern-formatter, custom-formatter]
--- Problems for relative address to root ["logging-profile" => "*","async-handler" => "*"]:
Different 'alternatives' for attribute 'formatter'. Current: ["named-formatter"]; legacy: undefined
Different 'alternatives' for parameter 'formatter' of operation 'add'. Current: ["named-formatter"]; legacy: undefined
Different 'alternatives' for parameter 'formatter' of operation 'update-properties'. Current: ["named-formatter"]; legacy: undefined
--- Problems for relative address to root ["logging-profile" => "*","console-handler" => "*"]:
Missing attributes in current: []; missing in legacy [named-formatter]
Different 'alternatives' for attribute 'formatter'. Current: ["named-formatter"]; legacy: undefined
Missing parameters for operation 'add' in current: []; missing in legacy [named-formatter]
Different 'alternatives' for parameter 'formatter' of operation 'add'. Current: ["named-formatter"]; legacy: undefined
Missing parameters for operation 'update-properties' in current: []; missing in legacy [named-formatter]
Different 'alternatives' for parameter 'formatter' of operation 'update-properties'. Current: ["named-formatter"]; legacy: undefined
--- Problems for relative address to root ["logging-profile" => "*","custom-handler" => "*"]:
Missing attributes in current: []; missing in legacy [named-formatter]
Different 'alternatives' for attribute 'formatter'. Current: ["named-formatter"]; legacy: undefined
Missing parameters for operation 'add' in current: []; missing in legacy [named-formatter]
Different 'alternatives' for parameter 'formatter' of operation 'add'. Current: ["named-formatter"]; legacy: undefined
Missing parameters for operation 'update-properties' in current: []; missing in legacy [named-formatter]
Different 'alternatives' for parameter 'formatter' of operation 'update-properties'. Current: ["named-formatter"]; legacy: undefined
--- Problems for relative address to root ["logging-profile" => "*","file-handler" => "*"]:
Missing attributes in current: []; missing in legacy [named-formatter]
Different 'alternatives' for attribute 'formatter'. Current: ["named-formatter"]; legacy: undefined
Missing parameters for operation 'add' in current: []; missing in legacy [named-formatter]
Different 'alternatives' for parameter 'formatter' of operation 'add'. Current: ["named-formatter"]; legacy: undefined
Missing parameters for operation 'update-properties' in current: []; missing in legacy [named-formatter]
Different 'alternatives' for parameter 'formatter' of operation 'update-properties'. Current: ["named-formatter"]; legacy: undefined
--- Problems for relative address to root ["logging-profile" => "*","periodic-rotating-file-handler" => "*"]:
Missing attributes in current: []; missing in legacy [named-formatter]
Different 'alternatives' for attribute 'formatter'. Current: ["named-formatter"]; legacy: undefined
Missing parameters for operation 'add' in current: []; missing in legacy [named-formatter]
Different 'alternatives' for parameter 'formatter' of operation 'add'. Current: ["named-formatter"]; legacy: undefined
Missing parameters for operation 'update-properties' in current: []; missing in legacy [named-formatter]
Different 'alternatives' for parameter 'formatter' of operation 'update-properties'. Current: ["named-formatter"]; legacy: undefined
--- Problems for relative address to root ["logging-profile" => "*","size-rotating-file-handler" => "*"]:
Missing attributes in current: []; missing in legacy [rotate-on-boot, named-formatter]
Different 'alternatives' for attribute 'formatter'. Current: ["named-formatter"]; legacy: undefined
Missing parameters for operation 'add' in current: []; missing in legacy [rotate-on-boot, named-formatter]
Different 'alternatives' for parameter 'formatter' of operation 'add'. Current: ["named-formatter"]; legacy: undefined
Missing parameters for operation 'update-properties' in current: []; missing in legacy [rotate-on-boot, named-formatter]
Different 'alternatives' for parameter 'formatter' of operation 'update-properties'. Current: ["named-formatter"]; legacy: undefined
--- Problems for relative address to root ["periodic-rotating-file-handler" => "*"]:
Missing attributes in current: []; missing in legacy [named-formatter]
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 'alternatives' for attribute 'formatter'. Current: ["named-formatter"]; legacy: undefined
Missing parameters for operation 'add' in current: []; missing in legacy [named-formatter]
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 'alternatives' for parameter 'formatter' of operation 'add'. Current: ["named-formatter"]; legacy: undefined
Missing parameters for operation 'update-properties' in current: []; missing in legacy [named-formatter]
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
Different 'alternatives' for parameter 'formatter' of operation 'update-properties'. Current: ["named-formatter"]; legacy: undefined
--- 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, named-formatter]
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 'alternatives' for attribute 'formatter'. Current: ["named-formatter"]; legacy: undefined
Missing parameters for operation 'add' in current: []; missing in legacy [rotate-on-boot, named-formatter]
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 'alternatives' for parameter 'formatter' of operation 'add'. Current: ["named-formatter"]; legacy: undefined
Missing parameters for operation 'update-properties' in current: []; missing in legacy [rotate-on-boot, named-formatter]
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
Different 'alternatives' for parameter 'formatter' of operation 'update-properties'. Current: ["named-formatter"]; legacy: undefined
====== Resource root address: ["subsystem" => "mail"] - Current version: 2.0.0; legacy version: 1.2.0 =======
====== Resource root address: ["subsystem" => "messaging"] - Current version: 2.0.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]
Missing child types in current: []; missing in legacy [servlet-connector]
--- Problems for relative address to root ["hornetq-server" => "*","address-setting" => "*"]:
Missing attributes in current: []; missing in legacy [expiry-delay]
Missing parameters for operation 'add' in current: []; missing in legacy [expiry-delay]
--- Problems for relative address to root ["hornetq-server" => "*","bridge" => "*"]:
Missing attributes in current: []; missing in legacy [reconnect-attempts-on-same-node]
Missing parameters for operation 'add' in current: []; missing in legacy [reconnect-attempts-on-same-node]
--- Problems for relative address to root ["hornetq-server" => "*","broadcast-group" => "*"]:
Different 'nillable' for attribute 'socket-binding'. Current: true; legacy: false
Different 'nillable' for parameter 'socket-binding' of operation 'add'. Current: true; legacy: false
--- 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" => "*","discovery-group" => "*"]:
Different 'nillable' for attribute 'socket-binding'. Current: true; legacy: false
Different 'nillable' for parameter 'socket-binding' of operation 'add'. Current: true; legacy: false
--- 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: 2.0.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]
--- Problems for relative address to root ["mod-cluster-config" => "configuration"]:
Missing attributes in current: []; missing in legacy [session-draining-strategy]
Missing parameters for operation 'add' in current: []; missing in legacy [session-draining-strategy]
====== Resource root address: ["subsystem" => "naming"] - Current version: 2.0.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: 2.0.0; legacy version: 1.2.0 =======
--- Problems for relative address to root []:
Different 'default' for attribute 'worker-task-max-threads'. Current: 8; legacy: 16
Missing child types in current: []; missing in legacy [http-connector]
--- Problems for relative address to root ["remote-outbound-connection" => "*"]:
Missing attributes in current: []; missing in legacy [protocol]
Missing parameters for operation 'add' in current: []; missing in legacy [protocol]
====== Resource root address: ["subsystem" => "resource-adapters"] - Current version: 2.0.0; legacy version: 1.2.0 =======
--- Problems for relative address to root ["resource-adapter" => "*"]:
Missing attributes in current: []; missing in legacy [wm-security-default-groups, wm-security-domain, wm-security, wm-security-mapping-group
s, wm-security-default-principal, wm-security-mapping-required, wm-security-mapping-users]
Missing parameters for operation 'add' in current: []; missing in legacy [wm-security-default-groups, wm-security-domain, wm-security, wm-se
curity-mapping-groups, wm-security-default-principal, wm-security-mapping-required, wm-security-mapping-users]
--- Problems for relative address to root ["resource-adapter" => "*","connection-definitions" => "*"]:
Missing attributes in current: []; missing in legacy [capacity-decrementer-class, capacity-incrementer-class, enlistment, sharable, capacity
-incrementer-properties, initial-pool-size, capacity-decrementer-properties]
Missing operations in current: []; missing in legacy [flush-gracefully-connection-in-pool, flush-invalid-connection-in-pool]
Missing parameters for operation 'add' in current: []; missing in legacy [capacity-decrementer-class, capacity-incrementer-class, enlistment
, sharable, capacity-incrementer-properties, initial-pool-size, capacity-decrementer-properties]
====== 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","auth-module" => "*"]:
Missing attributes in current: []; missing in legacy [module]
Missing parameters for operation 'add' in current: []; missing in legacy [module]
--- 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: 2.0.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" => "webservices"] - Current version: 1.2.0; legacy version: 1.2.0 =======
====== Resource root address: ["subsystem" => "weld"] - Current version: 2.0.0; legacy version: 1.0.0 =======
--- Problems for relative address to root []:
Missing attributes in current: []; missing in legacy [require-bean-descriptor, non-portable-mode]
Missing parameters for operation 'add' in current: []; missing in legacy [require-bean-descriptor, non-portable-mode]
Done comparison of STANDALONE!
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment