Code cleanup.
Use consistent class names for resource definitions and add/remove/describe operation handlers.
Try to minimize usage of static final variables.
Breakup CacheConfigOperationHandlers into individual add operation handlers for cache stores.
Traverse model via resource paths where possible.
Refactor/simplify the way we define and handle channel, cache and cache-container metrics
Incorporate code review feedback.
Move location and reduce visibility of the NAME attribute definition to help clarify that it is an *not* attribute of the CacheContainerResourceDefinition.
Remove WriteAttributeHandlers
Remove #registerDeploymentModel(final DescriptionProvider descriptionProvider)
Remove #registerSubsystemModel(DescriptionProvider descriptionProvider)
Remove #registerOperationHandler(String operationName, OperationStepHandler handler, DescriptionProvider descriptionProvider)
Remove #registerReadWriteAttribute(String attributeName, OperationStepHandler readHandler, OperationStepHandler writeHandler, AttributeAccess.Storage storage)
Remove #registerReadWriteAttribute(String attributeName, OperationStepHandler readHandler, OperationStepHandler writeHandler, EnumSet<AttributeAccess.Flag> flags)
Remove #registerReadOnlyAttribute(String attributeName, OperationStepHandler readHandler, EnumSet<AttributeAccess.Flag> flags)
Remove #registerMetric(String attributeName, OperationStepHandler metricHandler)
Remove #registerMetric(String attributeName, OperationStepHandler metricHandler, EnumSet<AttributeAccess.Flag> flags)
WFLY-3260 Fix WSTestCase
- remove unnecessary classes
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.
WFLY-3484 Update JSF based on Mojarra 2.2.7 and add a dependency on org.jboss.as.jsf to the org.jboss.as.jsf-injection module to fix JSF TCK failures
Ensure com.sun.security.auth.PolicyFile and IBM equiv is visible to controller module
[WFLY-3090] Ensure the latch gets counted down