[BZ1124086] Fixing failing test due to automatic keystore creation changes
https://issues.jboss.org/browse/WFCORE-202 Deadlock when shutdown Wildfly server during CLI client connection
[WFCORE-241] The default for http-upgrade-enabled is actually 'false'.
[WFCORE-231] Add version 3.0 of the schema for the Remoting subsystem.
[WFCORE-231] Update test configurations to use latest schema for the Remoting subsystem.
[WFCORE-231] Add support for specifying the server-name and sasl-protocol on the connectors.
[WFCORE-231] Minor namespace prefix issue in new schema.
[WFCORE-231] Set management API version to 3.0.0
[WFCORE-223] Make the version specific methods private and deleted the deprecated method as it is no longer used by WildFly.
[WFCORE-248] Correct should/must within error messages and check password does not match the username earlier in the validation.
[WFCORE-106] Add support to specify the sasl-protocol and server-name on each of the management interfaces.
[WFCORE-106] Add some core model tests that include the new attributes.
[WFCORE-246] Upgrade to JBoss SASL 1.0.5.CR1
[WFCORE-106] Further evolution of the SecurityRealm APIs to cover the scenarios required for obtaining an identity when using Remoting.
[WFCORE-106] Enable GSSAPI authentication where Kerberos is available as an authentication mechanism.
[WFCORE-104] Enable GSSAPI authentication for the CLI
[WFCORE-106] Correct the case for 'xs:string'.
[WFCORE-94] Enable -secmgr argument and SECMGR environment variable to turn on the security manager.
javac in JDK 8 doesn't play well with the new int and long primitive methods in jboss-logging. When an Integer or Long is used as the first parameter, casting the second primitive parameter to Object uses the correct logging method and doesn't confuse javac.
Merge pull request #175 from jamezp/WFCORE-94

[WFCORE-94] Facitilitate usage of -secmgr flag in startup scripts and propagate through domain