Make sure all JNDI entries are up before starting weld
Relace weld validation for EJB's
Current code was causing problems with remote views loaded from different class loaders
Fixes an issue with channel lifecycle that causes WFLY-2458.
Adds a hack to workaround ISPN-3697.
WFLY-2415 Add configuration option to enable/disable Infinispan statistics.
Cosmetic renaming
Convert InfinispanSubsystemXMLWriter to leverage AttributeDefinitions for marshalling.
Code cleanup.
Incorporate Kabir's feedback.
https://issues.jboss.org/browse/WFLY-2461 refactoring of character escaping in operation parameter values
https://issues.jboss.org/browse/WFLY-2464 simpler (than OBJECT) parser for STRING parameters and properties
[WFLY-1995], allow property substitution in some MDB Annotations.
WFLY-1571 deploying Seam apps
WFLY-2281 Testcase
WFLY-2281 Exception from lifecycle callback interceptor method intercepting a session bean is suppressed
[WFLY-2415] add statistics='true' to old domain configurations
WFLY-2491 Upgrade JGroups to 3.4.1.Final
WFLY-2374 Lifecycle callback interception tests for servlet components
WFLY-2477 Lifecycle callback methods not invoked on interceptors intercepting servlet component classes
Relax Weld injection point validation to the minimum required by the spec

Unfortunatly this is all a bit bogus at the moment, as weld has no way
of kowing where a class will be used, as classes can be used in different
modules with different entries bound to JNDI. For now we have just relaxed
the check to the minimum required to pass the CDI TCK.
WFLY-2481 CDI.current().getBeanManager() returns a beanmanager from a different deployment
[WFLY-2473] Upgrading to jbossws-cxf 4.2.3.Final