jboss - Override logging in WildFly -

I use Tomcat and just override the default logging system How to enable logging with wildback on wildfly in my Spring app can go?

My logback on Tomcat. XML Ok writing

  & lt ;? Xml version = "1.0" encoding = "UTF-8" & gt; & Lt; Configuration & gt; & Lt; Appender name = "STDOUT" class = "ch.qos.logback.core.ConsoleAppender" & gt; & Lt; Filter class = "ch.qos.logback.classic.filter.LevelFilter" & gt; & Lt; Levels & gt; Error & lt; / Level & gt; & Lt; OnMatch & gt; Accept & lt; / OnMatch & gt; & Lt; OnMismatch & gt; Denial & lt; / OnMismatch & gt; & Lt; / Filter & gt; & Lt; Encoder & gt; & Lt; Pattern & gt;% - 4relative [% Thread]% -5 Level% Logger {35} -% Message% n & lt; / Pattern & gt; & Lt; / Encoder & gt; & Lt; / Appender & gt; & Lt; Logger name = "org.springframework" level = "wARN" /> & Lt; Logger name = "com.citronium.planster" level = "INFO" /> & Lt; Logger name = "org.apache.http.impl.conn.tsccm" level = "ERROR" /> & Lt; Root level = "INFO" & gt; & Lt; Appender-Riffe = "STDOUT" /> & Lt; / Root & gt; & Lt; / Configuration & gt;  
 
 You can use logback to configure logging in your application. You can not use logback to configure logging for the server. 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 Structure.xml  which does not include subsystem. You must also include Logback and Slough 4G in your deployment. 
 
  The first option to change the add-logging-API-dependency  is a global setting for all deployments. The compliance value of the CLI command will change: 
 
  / subsystem = logging: list-attribute (name = ad-logging-API-dependencies, value = foil)  
 < P> This option only does not add any logging dependency to your deployment. The second option to use  jboss-deployment-structure.xml  will disable logging. The subsystem for your deployment is only the following one example file: 
 
  & lt; Jboss-deployment-structure & gt; & Lt; Deployment & gt; & Lt ;! - The deprecated subsystem prevents a sub-system deployment unit from running on a deployment processor - & gt; & Lt ;! - which basically gives the same effect of removing the subsystem, but it only affects single deployment - & gt; & Lt; To the outside sub & gt; & Lt; Subsystem name = "logging" /> & Lt; / Out-side & gt; & Lt; / Deployment & gt; & Lt; / Jboss deployment structure & gt;