[WFLY-3822] Also update jbossws-common
[JBWS-3809] AbstractDeployment#addEndpoint's check on urlPattern performed on wrong data
Merge pull request #6728 from asoldano/8.x

[8.x][WFLY-3822] Complete upgrade to JBossWS 4.3.1.Final
Revert "[WFLY-3507] : Adding support for defining more url-patterns for the JspServlet in a web application."

This reverts commit 38b46e6293e955ee4b13af7a24ef4bbd405bb201.
WFLY-3102 EJB in war should inherit the default security domain
WFLY-1891 Session sharing for non-clustered sessions
Remove PersistentResourceDefinitionBuilder.addAttributes(Collection)

This version of the method is problematic because any changes to the underling
list will cause existing parsers to change. In particular if an attribute is added
or removed this change will affect old versions of the parser.
WFLY-998 RunAs does not work for Servlet init() methods
WFLY-3300 Provide a way to change SSO session id cookie name
fix undertow parser
WFLY-3448 Make sure to use the correct context path when application is deployed to the context root
Fix some Undertow permissions issues
WFLY-3391 Make sure that multipart servlet config can be specified for the default servlet
WFLY-3514 Make sure JASPIAuthenticationMechanism only wraps the request once
[WFLY-3507] : Adding support for defining more url-patterns for the JspServlet in a web application.
ServletContext.getVirtualServerName always returns "localhost"

I experimented with the new getVirtualServerName method introduced for interface ServletContext in servlet spec 3.1. The JavaDoc states: Returns the primary name of the virtual host on which this context is deployed. The name may or may not be a valid host name.

However Wildfly always seems to return "localhost" instead of the virtual host name specified in XML configuration files. My host config in standalone.xml looks like this: <host name="default-host" alias="www.sample.com">. I expected that getVirtualServerName returns "default-host" in this case.

getVirtualServerName is implemented like this: "return deployment.getDeploymentInfo().getHostName();". However DeploymentInfo.setHostName is never called during startup.

If I did not misunderstand what getVirtualServerName is supposed to deliver, something similar to my proposed patch should fix the problem. Sorry, I only looked at Wildfly source code for the first time today in a debugger and was unable to verify if my proposed patch compiles :( Hope a more experienced developer can have a quick look.
Add Read & Write timeouts configuration options

- undertow 2.0 schema & model
WFLY-3516 New XMLNS for JSTL tags not recognized (http://xmlns.jcp.org/jsp/jstl/core)
WFLY-3626 when calling JAASIdentityManager.verify make sure the principal that is used is the original principal
Fix potential JASPIC NPE