anchor.diff:  API, then you have a single place to configure and manage logging.
   
   A common choice might be to bridge Spring to SLF4J, and then provide explicit binding
  -from SLF4J to Log4J. You need to supply 4 dependencies (and exclude the existing
  -`commons-logging`): the bridge, the SLF4J API, the binding to Log4J, and the Log4J
  -implementation itself. In Maven you would do that like this
  +from SLF4J to Log4j. You need to supply several dependencies (and exclude the existing
  +`commons-logging`): the bridge, the SLF4J implementation for Log4j, and the Log4j
  +implementation itself. In Maven you would do that like this:
   
   [source,xml,indent=0]
   [subs="verbatim,quotes,attributes"]
  
positive.code: 
  To be clear about this: the problems reported are usually not with JCL per se, or even
  with `commons-logging`: rather they are to do with binding `commons-logging` to another
  framework (often Log4J). This can fail because `commons-logging` changed the way they do
  the runtime discovery in between the older versions (1.0) found in some containers and
  the modern versions that most people use now (1.1). Spring does not use any unusual
  parts of the JCL API, so nothing breaks there, but as soon as Spring or your application
  tries to do any logging you can find that the bindings to Log4J are not working.
  
  In such cases with WAS the easiest thing to do is to invert the class loader hierarchy
  (IBM calls it "parent last") so that the application controls the JCL dependency, not
  
negative.code: 			<version>1.7.22</version>
  		</dependency>
  		<dependency>
  			<groupId>org.apache.logging.log4j</groupId>
  			<artifactId>log4j-slf4j-impl</artifactId>
  			<version>2.7</version>
  		</dependency>
  		<dependency>
  			<groupId>org.apache.logging.log4j</groupId>
  			<artifactId>log4j-api</artifactId>
  			<version>2.7</version>
  		</dependency>
  		<dependency>
  			<groupId>org.apache.logging.log4j</groupId>
  			<artifactId>log4j-core</artifactId>
  			<version>2.7</version>
  		</dependency>
  	</dependencies>
  ----
  