Custom env profile for SLF4J parametrization - ArnaudGarnierCAST/com.castsoftware.uc.slf4j.param GitHub Wiki
When your Java application uses SLF4J as logging framework. This can be detected:
- Before analysis :
-
from the application survey
-
from the presence of JAR, for instance : slf4j-api-1.7.5.jar
-
from the presence of slf4j-api dependency in Maven pom.xml file
<dependency><groupId>org.slf4j</groupId><artifactId>slf4j-api</artifactId></dependency> -
from the presence of following import in .java source files:
-
import org.slf4j.Logger;
import org.slf4j.LoggerFactory;
- After analysis :
- from presence in Analysis Service of external class and methods from package org.slf4j
org.slf4j.Logger.debugororg.slf4j.Logger.infoororg.slf4j.Logger.warn...
- from presence in Analysis Service of external class and methods from package org.slf4j
All versions of SLF4j are supported, from 1.0 to 1.7.x.
All AIP versions AIP 7.0.x to 8.2.0 are supported
- Import : Edit Analysis Service, and use tab Environment Profile / Import... to import the .aex file provided here.
-
Add this custom environment profile at Application level :
- Edit Application
- go to Frameworks panel
- in Custom J2EE Environment profiles, click Add..., and select the SLF4J env profile in the list.
These parametrization rules will prevent External Link engine (grep tool) to draw Use links towards DB objects whose name are found in argument's strings. This will avoid to overcrowd the list of dynamic links the AI admin has to validate in DLM (Dynamic Link Manager).
Current version does not parametrize logger methods decorated with Marker data (using the Marker parameter). They can be added at will.