During the process of upgrading to WildFly 11, an issue with embedded WildFly and JBoss Logging was discovered. Here are the critical details:

1. A third-party dependency (TODO: record which one here) included in the SDM webapp uses JBoss Logging
2. JBoss Logging uses the global Java logging infrastructure. Importantly, the JBoss LogManager must be setup before any other code uses a logger.
3. The GWT compiler uses Java logging
4. Since (in our setup) GWT launches the application server, it is impossible to configure the log manager from within WildFly
5. Setting up JBoss Logging before GWT launches is also not an option, because of the WF classloader. Dependencies attempting to use JBoss Logging in a webapp will get class cast exceptions.

So far the only possible remedies to pursue are:

1. Don't use an embedded WildFly instance.
2. Avoid using JBoss Logging (even transitively) in the platform.