Differences with 7.1.2.Final

gistfile1.txt

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


Different 'value-type' for 'reply-properties' for operation 'read-attribute'. Current: OBJECT; legacy: undefined
>>> it shows as
        "reply-properties" => {
            "description" => "The description of the resource",
            "type" => OBJECT,
            "value-type" => OBJECT
        },
I think it should just be, i.e. no value-type
        "reply-properties" => {
            "description" => "The description of the resource",
            "type" => OBJECT
        },


Different 'nillable' for parameter 'child-type' of operation 'read-children-names'. Current: true; legacy: false
<< Should not be nillable
Different 'nillable' for parameter 'child-type' of operation 'read-children-resources'. Current: true; legacy: false
<< Should not be nillable
Different 'value-type' for 'reply-properties' for operation 'read-operation-description'. Current: OBJECT; legacy: undefined
<< I think there should be no value-type (see above)

Missing parameters for operation 'read-resource' in current: []; missing in legacy [attributes-only, include-aliases]
<< ok
Different 'value-type' for 'reply-properties' for operation 'read-resource'. Current: OBJECT; legacy: undefined
<< I think there should be no value-type (see above)
Missing parameters for operation 'read-resource-description' in current: []; missing in legacy [include-aliases]
<< ok
Different 'value-type' for 'reply-properties' for operation 'read-resource-description'. Current: OBJECT; legacy: undefined
<< I think there should be no value-type (see above)
Missing child types in current: []; missing in legacy [deployment-overlay]
<< ok

--- 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]
<<<< Fixed in branch

--- 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 practise

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
<<< see https://gist.github.com/3762099

--- 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; leg
acy: true

Different 'expressions-allowed' for value-type key 'host' for value-type key 'remote' for attribute 'domain-controller'. Current: false; leg
acy: true
Different 'nillable' for value-type key 'remote' for attribute 'domain-controller'. Current: true; legacy: false
Different 'nillable' for value-type key 'local' for attribute 'domain-controller'. Current: true; legacy: false
Different 'nillable' for attribute 'master'. Current: true; legacy: false
Different 'storage' for attribute 'master'. Current: "configuration"; legacy: "runtime"
Different 'nillable' for attribute 'release-codename'. Current: true; legacy: false
Different 'nillable' for attribute 'release-version'. Current: true; legacy: false
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]
Missing parameters for operation 'reload' in current: []; missing in legacy [use-current-host-config, use-current-domain-config]
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
Missing child types in current: [extension]; missing in legacy []
--- Problems for relative address to root ["core-service" => "management","security-realm" => "*","authentication" => "users","user" => "*"]
:
Different 'expressions-allowed' for attribute 'password'. Current: true; legacy: false
Different 'expressions-allowed' for parameter 'password' of operation 'add'. Current: true; legacy: false
--- Problems for relative address to root ["core-service" => "platform-mbean","type" => "compilation"]:
Missing parameters for operation 'read-resource' in current: []; missing in legacy [attributes-only, include-aliases]
Different 'value-type' for 'reply-properties' for operation 'read-resource'. Current: OBJECT; legacy: undefined
--- Problems for relative address to root ["core-service" => "platform-mbean","type" => "memory-pool","name" => "*"]:
Missing parameters for operation 'read-resource' in current: []; missing in legacy [attributes-only, include-aliases]
Different 'value-type' for 'reply-properties' for operation 'read-resource'. Current: OBJECT; legacy: undefined
--- Problems for relative address to root ["core-service" => "platform-mbean","type" => "operating-system"]:
Missing parameters for operation 'read-resource' in current: []; missing in legacy [attributes-only, include-aliases]
Different 'value-type' for 'reply-properties' for operation 'read-resource'. Current: OBJECT; legacy: undefined
--- Problems for relative address to root ["core-service" => "platform-mbean","type" => "runtime"]:
Missing parameters for operation 'read-resource' in current: []; missing in legacy [attributes-only, include-aliases]
Different 'value-type' for 'reply-properties' for operation 'read-resource'. Current: OBJECT; legacy: undefined
--- Problems for relative address to root ["core-service" => "platform-mbean","type" => "threading"]:
Missing parameters for operation 'read-resource' in current: []; missing in legacy [attributes-only, include-aliases]
Different 'value-type' for 'reply-properties' for operation 'read-resource'. Current: OBJECT; legacy: undefined
--- Problems for relative address to root ["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 ["path" => "*"]:
Different 'expressions-allowed' for attribute 'path'. Current: true; legacy: false
Different 'type' for attribute 'read-only'. Current: BOOLEAN; legacy: STRING
Different 'expressions-allowed' for parameter 'path' of operation 'add'. Current: true; legacy: false
--- 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
Different 'expressions-allowed' for attribute 'auto-start'. Current: true; legacy: false
Different 'expressions-allowed' for attribute 'group'. Current: true; legacy: false
Different 'nillable' for attribute 'socket-binding-group'. Current: true; legacy: false
Different 'expressions-allowed' for attribute 'socket-binding-group'. Current: true; legacy: false
Different 'type' for attribute 'socket-binding-port-offset'. Current: STRING; legacy: INT
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
--- 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
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
--- 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
====== Comparing subsystem models ======

Done comparison!



>>>> STANDALONE
====== 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]
Different 'nillable' for attribute 'profile-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: fal
se
Different 'nillable' for parameter 'runtime-name' of operation 'full-replace-deployment'. Current: true; legacy: false
Different 'value-type' for 'reply-properties' for operation 'read-attribute'. Current: OBJECT; legacy: undefined
Different 'nillable' for parameter 'child-type' of operation 'read-children-names'. Current: true; legacy: false
Different 'nillable' for parameter 'child-type' of operation 'read-children-resources'. Current: true; legacy: false
Different 'value-type' for 'reply-properties' for operation 'read-operation-description'. Current: OBJECT; legacy: undefined
Missing parameters for operation 'read-resource' in current: []; missing in legacy [attributes-only, include-aliases]
Different 'value-type' for 'reply-properties' for operation 'read-resource'. Current: OBJECT; legacy: undefined
Missing parameters for operation 'read-resource-description' in current: []; missing in legacy [include-aliases]
Different 'value-type' for 'reply-properties' for operation 'read-resource-description'. Current: OBJECT; legacy: undefined
Missing parameters for operation 'reload' in current: []; missing in legacy [use-current-server-config]
Missing parameters for operation 'replace-deployment' in current: []; missing in legacy [content]
Missing child types in current: []; missing in legacy [deployment-overlay]
--- Problems for relative address to root ["core-service" => "management","security-realm" => "*","authentication" => "users","user" => "*"]
:
Different 'expressions-allowed' for attribute 'password'. Current: true; legacy: false
Different 'expressions-allowed' for parameter 'password' of operation 'add'. Current: true; legacy: false
--- Problems for relative address to root ["core-service" => "platform-mbean","type" => "compilation"]:
Missing parameters for operation 'read-resource' in current: []; missing in legacy [attributes-only, include-aliases]
Different 'value-type' for 'reply-properties' for operation 'read-resource'. Current: OBJECT; legacy: undefined
--- Problems for relative address to root ["core-service" => "platform-mbean","type" => "memory-pool","name" => "*"]:
Missing parameters for operation 'read-resource' in current: []; missing in legacy [attributes-only, include-aliases]
Different 'value-type' for 'reply-properties' for operation 'read-resource'. Current: OBJECT; legacy: undefined
--- Problems for relative address to root ["core-service" => "platform-mbean","type" => "operating-system"]:
Missing parameters for operation 'read-resource' in current: []; missing in legacy [attributes-only, include-aliases]
Different 'value-type' for 'reply-properties' for operation 'read-resource'. Current: OBJECT; legacy: undefined
--- Problems for relative address to root ["core-service" => "platform-mbean","type" => "runtime"]:
Missing parameters for operation 'read-resource' in current: []; missing in legacy [attributes-only, include-aliases]
Different 'value-type' for 'reply-properties' for operation 'read-resource'. Current: OBJECT; legacy: undefined
--- Problems for relative address to root ["core-service" => "platform-mbean","type" => "threading"]:
Missing parameters for operation 'read-resource' in current: []; missing in legacy [attributes-only, include-aliases]
Different 'value-type' for 'reply-properties' for operation 'read-resource'. Current: OBJECT; legacy: undefined
--- 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 attribute 'enabled'. 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
Different 'nillable' for parameter 'enabled' of operation 'add'. Current: true; legacy: false
--- Problems for relative address to root ["deployment" => "*","subdeployment" => "*"]:
Missing child names for type=subsystem in current: [messaging]; missing in legacy []
--- Problems for relative address to root ["deployment" => "*","subdeployment" => "*","subsystem" => "jpa"]:
Missing attributes in current: []; missing in legacy [default-datasource]
Missing operations in current: []; missing in legacy [remove, add]
Missing child names for type=subsystem in current: [messaging]; missing in legacy []
--- Problems for relative address to root ["deployment" => "*","subsystem" => "jpa"]:
Missing attributes in current: []; missing in legacy [default-datasource]
Missing operations in current: []; missing in legacy [remove, add]
--- Problems for relative address to root ["extension" => "*","subsystem" => "*"]:
Missing attributes in current: []; missing in legacy [management-micro-version]
--- Problems for relative address to root ["interface" => "*"]:
Missing attributes in current: []; missing in legacy [resolved-address]
--- Problems for relative address to root ["path" => "*"]:
Different 'expressions-allowed' for attribute 'path'. Current: true; legacy: false
Different 'type' for attribute 'read-only'. Current: BOOLEAN; legacy: STRING
Different 'expressions-allowed' for parameter 'path' of operation 'add'. Current: true; legacy: false
--- Problems for relative address to root ["system-property" => "*"]:
Different 'nillable' for attribute 'value'. Current: true; legacy: false
Different 'expressions-allowed' for attribute 'value'. Current: true; legacy: false
====== Comparing subsystem models ======
-- SNIP ---