Skip to content

Instantly share code, notes, and snippets.

@ctomc
Forked from kabir/gist:3783311
Created September 25, 2012 19:23
Show Gist options
  • Save ctomc/3783892 to your computer and use it in GitHub Desktop.
Save ctomc/3783892 to your computer and use it in GitHub Desktop.
Differences with 7.1.2.Final, second try
These are all with Report on differences in the model when the management versions are different? y/[n]: y
>>>>>DOMAIN
====== Comparing core models ======
====== Resource root address: [] - Current version: 1.4.0; legacy version: 1.2.0 =======
--- Problems for relative address to root []:
Missing attributes in current: []; missing in legacy [launch-type]
<<ok
Different 'nillable' for attribute 'local-host-name'. Current: true; legacy: false
<< ok
Different 'nillable' for value-type key 'path' for parameter 'content' of operation 'full-replace-deployment'. Current: true; legacy: false
<<ok
Different 'nillable' for value-type key 'archive' for parameter 'content' of operation 'full-replace-deployment'. Current: true; legacy: fal
se
<< ok
Different 'nillable' for parameter 'runtime-name' of operation 'full-replace-deployment'. Current: true; legacy: false
<< ok
Missing parameters for operation 'read-resource' in current: []; missing in legacy [attributes-only, include-aliases]
<< ok, was added for 7.2
Missing parameters for operation 'read-resource-description' in current: []; missing in legacy [include-aliases]
<< ok, was added for 7.2
Missing parameters for operation 'reload' in current: []; missing in legacy [use-current-server-config]
<< ok, was added for 7.2
Missing child types in current: []; missing in legacy [deployment-overlay]
<< this is ok, overlays added in 7.2
--- Problems for relative address to root ["deployment" => "*"]:
Missing value-type for attribute 'content' in current: [bytes, input-stream-index, url]; missing in legacy []
Different 'nillable' for value-type key 'path' for attribute 'content'. Current: true; legacy: false
Different 'nillable' for value-type key 'archive' for attribute 'content'. Current: true; legacy: false
Different 'nillable' for value-type key 'path' for parameter 'content' of operation 'add'. Current: true; legacy: false
Different 'nillable' for value-type key 'archive' for parameter 'content' of operation 'add'. Current: true; legacy: false
<<< These are ok, see https://gist.github.com/3762099
--- Problems for relative address to root ["extension" => "*","subsystem" => "*"]:
Missing attributes in current: []; missing in legacy [management-micro-version]
<< ok
--- Problems for relative address to root ["path" => "*"]:
Different 'type' for attribute 'read-only'. Current: BOOLEAN; legacy: STRING
<< Sounds ok
--- Problems for relative address to root ["profile" => "*"]:
Different 'type' for attribute 'name'. Current: STRING; legacy: undefined
<< Should be ok
Missing parameters for operation 'add' in current: []; missing in legacy [name]
<<<< Perhaps I (kabir) should not include this in the add operation?
<<<< Fixed (Tomaz) added .setResourceOnly() for name
--- Problems for relative address to root ["server-group" => "*"]:
Different 'nillable' for attribute 'management-subsystem-endpoint'. Current: true; legacy: false
<<< It now has default of false
Different 'nillable' for attribute 'socket-binding-port-offset'. Current: true; legacy: false
<<< Nillable was allowed in practice
Missing parameters for operation 'add' in current: [jvm]; missing in legacy []
<<< This was old rubbish
Different 'nillable' for parameter 'management-subsystem-endpoint' of operation 'add'. Current: true; legacy: false
<<< Default is false
Different 'nillable' for parameter 'socket-binding-port-offset' of operation 'add'. Current: true; legacy: false
<<< Nillable was allowed in practise
Missing child types in current: []; missing in legacy [deployment-overlay]
<<< should be ok
--- Problems for relative address to root ["server-group" => "*","deployment" => "*"]:
Different 'nillable' for attribute 'enabled'. Current: true; legacy: false
Missing parameters for operation 'add' in current: [content]; missing in legacy []
Different 'nillable' for parameter 'enabled' of operation 'add'. Current: true; legacy: false
<<< ok
--- Problems for relative address to root ["server-group" => "*","jvm" => "*"]:
Different 'type' for attribute 'environment-variables'. Current: OBJECT; legacy: LIST
Different 'value-type' for attribute 'environment-variables'. Current: STRING; legacy: PROPERTY
Different 'type' for parameter 'environment-variables' of operation 'add'. Current: OBJECT; legacy: LIST
Different 'value-type' for parameter 'environment-variables' of operation 'add'. Current: STRING; legacy: PROPERTY
<<< AFAICR these should be ok
--- Problems for relative address to root ["server-group" => "*","system-property" => "*"]:
Different 'nillable' for attribute 'boot-time'. Current: true; legacy: false
Different 'nillable' for attribute 'value'. Current: true; legacy: false
Different 'expressions-allowed' for attribute 'value'. Current: true; legacy: false
<<< AFAICR these should be ok
--- Problems for relative address to root ["system-property" => "*"]:
Different 'nillable' for attribute 'boot-time'. Current: true; legacy: false
Different 'nillable' for attribute 'value'. Current: true; legacy: false
Different 'expressions-allowed' for attribute 'value'. Current: true; legacy: false
<<< AFAICR these should be ok
====== Comparing subsystem models ======
Done comparison!
>>>> HOST
====== Comparing core models ======
====== Resource root address: [] - Current version: 1.4.0; legacy version: 1.2.0 =======
--- Problems for relative address to root []:
Missing attributes in current: []; missing in legacy [running-mode, host-state]
Different 'type' for value-type key 'port' for value-type key 'remote' for attribute 'domain-controller'. Current: INT; legacy: STRING
<<< ok
Different 'expressions-allowed' for value-type key 'port' for value-type key 'remote' for attribute 'domain-controller'. Current: false; legacy: true
Different 'expressions-allowed' for value-type key 'host' for value-type key 'remote' for attribute 'domain-controller'. Current: false; legacy: true
<< fixed
Different 'nillable' for value-type key 'remote' for attribute 'domain-controller'. Current: true; legacy: false
<< fixed
Different 'nillable' for value-type key 'local' for attribute 'domain-controller'. Current: true; legacy: false
<< fixed
Different 'nillable' for attribute 'master'. Current: true; legacy: false
<< fixed
Different 'storage' for attribute 'master'. Current: "configuration"; legacy: "runtime"
<< fixed
Different 'nillable' for attribute 'release-codename'. Current: true; legacy: false
<< ok
Different 'nillable' for attribute 'release-version'. Current: true; legacy: false
<< ok
Different 'nillable' for attribute 'server-state'. Current: true; legacy: false
Different 'storage' for attribute 'server-state'. Current: "runtime"; legacy: "configuration"
Missing operations in current: []; missing in legacy [validate-address]
<< ok
Missing parameters for operation 'reload' in current: []; missing in legacy [use-current-host-config, use-current-domain-config]
<< added in 7.2
Missing parameters for operation 'write-remote-domain-controller' in current: []; missing in legacy [username, security-realm]
Different 'type' for parameter 'port' of operation 'write-remote-domain-controller'. Current: INT; legacy: STRING
<< legacy was wrong, and write-remote-domain-controler didn't actually work till 7.2
Missing child types in current: [extension]; missing in legacy []
<< might be right? Kabir?
--- Problems for relative address to root ["core-service" => "management","security-realm" => "*","authentication" => "users","user" => "*"]:
Different 'expressions-allowed' for attribute 'password'. Current: true; legacy: false
<< ok
Different 'expressions-allowed' for parameter 'password' of operation 'add'. Current: true; legacy: false
<< ok
Missing parameters for operation 'read-resource' in current: []; missing in legacy [attributes-only, include-aliases]
<< added in 7.2
--- Problems for relative address to root ["core-service" => "vault"]:
Different 'nillable' for parameter 'code' of operation 'add'. Current: true; legacy: false
<< legacy was wrong
Different 'nillable' for parameter 'vault-options' of operation 'add'. Current: true; legacy: false
<< legacy was wrong
--- Problems for relative address to root ["jvm" => "*"]:
Different 'type' for attribute 'environment-variables'. Current: OBJECT; legacy: LIST
<< ok
Different 'value-type' for attribute 'environment-variables'. Current: STRING; legacy: PROPERTY
<< ok
Different 'type' for parameter 'environment-variables' of operation 'add'. Current: OBJECT; legacy: LIST
<< ok
Different 'value-type' for parameter 'environment-variables' of operation 'add'. Current: STRING; legacy: PROPERTY
<< ok
--- Problems for relative address to root ["path" => "*"]:
Different 'expressions-allowed' for attribute 'path'. Current: true; legacy: false
<< ok
Different 'type' for attribute 'read-only'. Current: BOOLEAN; legacy: STRING
<< ok
Different 'expressions-allowed' for parameter 'path' of operation 'add'. Current: true; legacy: false
<< ok
--- Problems for relative address to root ["server-config" => "*"]:
Missing attributes in current: []; missing in legacy [cpu-affinity, status, priority]
Different 'nillable' for attribute 'auto-start'. Current: true; legacy: false
<< ok
Different 'expressions-allowed' for attribute 'auto-start'. Current: true; legacy: false
<< ok
Different 'expressions-allowed' for attribute 'group'. Current: true; legacy: false
<< ok
Different 'nillable' for attribute 'socket-binding-group'. Current: true; legacy: false
<< ok
Different 'expressions-allowed' for attribute 'socket-binding-group'. Current: true; legacy: false
<< ok
Different 'type' for attribute 'socket-binding-port-offset'. Current: STRING; legacy: INT
<< fixed
Different 'nillable' for attribute 'socket-binding-port-offset'. Current: true; legacy: false
Different 'expressions-allowed' for attribute 'socket-binding-port-offset'. Current: true; legacy: false
Missing parameters for operation 'add' in current: []; missing in legacy [cpu-affinity, priority]
Different 'nillable' for parameter 'auto-start' of operation 'add'. Current: true; legacy: false
Different 'expressions-allowed' for parameter 'auto-start' of operation 'add'. Current: true; legacy: false
Different 'expressions-allowed' for parameter 'group' of operation 'add'. Current: true; legacy: false
Different 'nillable' for parameter 'socket-binding-group' of operation 'add'. Current: true; legacy: false
Different 'expressions-allowed' for parameter 'socket-binding-group' of operation 'add'. Current: true; legacy: false
Different 'type' for parameter 'socket-binding-port-offset' of operation 'add'. Current: STRING; legacy: INT
Different 'nillable' for parameter 'socket-binding-port-offset' of operation 'add'. Current: true; legacy: false
Different 'expressions-allowed' for parameter 'socket-binding-port-offset' of operation 'add'. Current: true; legacy: false
<< all sockets ok
--- Problems for relative address to root ["server-config" => "*","jvm" => "*"]:
Different 'type' for attribute 'environment-variables'. Current: OBJECT; legacy: LIST
Different 'value-type' for attribute 'environment-variables'. Current: STRING; legacy: PROPERTY
Different 'type' for parameter 'environment-variables' of operation 'add'. Current: OBJECT; legacy: LIST
Different 'value-type' for parameter 'environment-variables' of operation 'add'. Current: STRING; legacy: PROPERTY
--- Problems for relative address to root ["server-config" => "*","path" => "*"]:
Different 'expressions-allowed' for attribute 'path'. Current: true; legacy: false
Different 'type' for attribute 'read-only'. Current: BOOLEAN; legacy: STRING
<< ok
Different 'expressions-allowed' for parameter 'path' of operation 'add'. Current: true; legacy: false
--- Problems for relative address to root ["server-config" => "*","system-property" => "*"]:
Different 'nillable' for attribute 'boot-time'. Current: true; legacy: false
Different 'nillable' for attribute 'value'. Current: true; legacy: false
Different 'expressions-allowed' for attribute 'value'. Current: true; legacy: false
Different 'expressions-allowed' for parameter 'value' of operation 'add'. Current: true; legacy: false
<< ok
--- Problems for relative address to root ["system-property" => "*"]:
Different 'nillable' for attribute 'boot-time'. Current: true; legacy: false
Different 'nillable' for attribute 'value'. Current: true; legacy: false
Different 'expressions-allowed' for attribute 'value'. Current: true; legacy: false
Different 'expressions-allowed' for parameter 'value' of operation 'add'. Current: true; legacy: false
====== Comparing subsystem models ======
Done comparison!
DOMAIN!!
====== Comparing core models ======
====== Resource root address: [] - Current version: 1.4.0; legacy version: 1.2.0 =======
--- Problems for relative address to root []:
Missing attributes in current: []; missing in legacy [launch-type]
Different 'nillable' for attribute 'local-host-name'. Current: true; legacy: false
Different 'nillable' for value-type key 'path' for parameter 'content' of operation 'full-replace-deployment'. Current: true; legacy: false
Different 'nillable' for value-type key 'archive' for parameter 'content' of operation 'full-replace-deployment'. Current: true; legacy: false
Different 'nillable' for parameter 'runtime-name' of operation 'full-replace-deployment'. Current: true; legacy: false
Missing parameters for operation 'read-resource' in current: []; missing in legacy [attributes-only, include-aliases]
Missing parameters for operation 'read-resource-description' in current: []; missing in legacy [include-aliases]
Missing child types in current: []; missing in legacy [deployment-overlay]
--- Problems for relative address to root ["deployment" => "*"]:
Missing value-type for attribute 'content' in current: [bytes, input-stream-index, url]; missing in legacy []
Different 'nillable' for value-type key 'path' for attribute 'content'. Current: true; legacy: false
Different 'nillable' for value-type key 'archive' for attribute 'content'. Current: true; legacy: false
Different 'nillable' for value-type key 'path' for parameter 'content' of operation 'add'. Current: true; legacy: false
Different 'nillable' for value-type key 'archive' for parameter 'content' of operation 'add'. Current: true; legacy: false
--- Problems for relative address to root ["extension" => "*","subsystem" => "*"]:
Missing attributes in current: []; missing in legacy [management-micro-version]
--- Problems for relative address to root ["path" => "*"]:
Different 'type' for attribute 'read-only'. Current: BOOLEAN; legacy: STRING
--- Problems for relative address to root ["profile" => "*"]:
Different 'type' for attribute 'name'. Current: STRING; legacy: undefined
--- Problems for relative address to root ["server-group" => "*"]:
Different 'nillable' for attribute 'management-subsystem-endpoint'. Current: true; legacy: false
Different 'nillable' for attribute 'socket-binding-port-offset'. Current: true; legacy: false
Missing parameters for operation 'add' in current: [jvm]; missing in legacy []
Different 'nillable' for parameter 'management-subsystem-endpoint' of operation 'add'. Current: true; legacy: false
Different 'nillable' for parameter 'socket-binding-port-offset' of operation 'add'. Current: true; legacy: false
Missing child types in current: []; missing in legacy [deployment-overlay]
--- Problems for relative address to root ["server-group" => "*","deployment" => "*"]:
Different 'nillable' for attribute 'enabled'. Current: true; legacy: false
Missing parameters for operation 'add' in current: [content]; missing in legacy []
Different 'nillable' for parameter 'enabled' of operation 'add'. Current: true; legacy: false
--- Problems for relative address to root ["server-group" => "*","jvm" => "*"]:
Different 'type' for attribute 'environment-variables'. Current: OBJECT; legacy: LIST
Different 'value-type' for attribute 'environment-variables'. Current: STRING; legacy: PROPERTY
Different 'type' for parameter 'environment-variables' of operation 'add'. Current: OBJECT; legacy: LIST
Different 'value-type' for parameter 'environment-variables' of operation 'add'. Current: STRING; legacy: PROPERTY
--- Problems for relative address to root ["server-group" => "*","system-property" => "*"]:
Different 'nillable' for attribute 'boot-time'. Current: true; legacy: false
Different 'nillable' for attribute 'value'. Current: true; legacy: false
Different 'expressions-allowed' for attribute 'value'. Current: true; legacy: false
Different 'expressions-allowed' for parameter 'value' of operation 'add'. Current: true; legacy: false
--- Problems for relative address to root ["system-property" => "*"]:
Different 'nillable' for attribute 'boot-time'. Current: true; legacy: false
Different 'nillable' for attribute 'value'. Current: true; legacy: false
Different 'expressions-allowed' for attribute 'value'. Current: true; legacy: false
Different 'expressions-allowed' for parameter 'value' of operation 'add'. Current: true; legacy: false
====== Comparing subsystem models ======
Done comparison!
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment