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.
WFLY-3260 Fix WSTestCase
- remove unnecessary classes
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-3517] Properly shut down the TempFileProvider thread pool
[[WFLY-3493] Do not remove a JMS resource with deployed dependencies

Ensure that there is a dependency between the JMS resource service
(JMSQueueService and JMSTopicService) and the BinderService for their
JNDI bindings so that if the resource is removed, the missing dependency
is detected.

Add recovering of the JMSQueue and JMSTopic services in the :remove
operations by replaying the runtime part of their corresponding :add
operations.

JIRA: https://issues.jboss.org/browse/WFLY-3493
Fix schema location rebase issue after build split

I forgot to move new schemas that were added after the initial split
first stab at core domain tests
use wildfly-core target directory
move RBAC tests over
Move CLI tests
moved DomainTestSuite
Make RBAC tests pass
split testsuite shared
Fix checkstyle
add ts.domain maven profile
Fix WildCardReadsTestCase to use non wildcard resource
WFLY-3440 Split up Java EE dependency processor into the appropriate subsystems