uk.gov.hmrc.play.bootstrap.filters
Members list
Type members
Classlikes
Attributes
- Supertypes
-
trait EssentialFilterclass Objecttrait Matchableclass Any
- Known subtypes
-
trait CommonAuditFilter
Attributes
- Companion
- object
- Supertypes
-
trait Serializabletrait Producttrait Equalsclass Objecttrait Matchableclass AnyShow all
Attributes
- Companion
- class
- Supertypes
-
trait Producttrait Mirrorclass Objecttrait Matchableclass Any
- Self type
-
CacheControlConfig.type
Attributes
- Companion
- object
- Supertypes
-
trait Filtertrait EssentialFilterclass Objecttrait Matchableclass Any
Attributes
- Companion
- class
- Supertypes
-
class Objecttrait Matchableclass Any
- Self type
-
CacheControlFilter.type
Attributes
- Supertypes
Attributes
- Supertypes
-
trait LoggingFiltertrait Filtertrait EssentialFilterclass Objecttrait Matchableclass AnyShow all
Attributes
- Companion
- object
- Supertypes
-
trait Serializabletrait Producttrait Equalsclass Objecttrait Matchableclass AnyShow all
Attributes
- Supertypes
-
trait Filtertrait EssentialFilterclass Objecttrait Matchableclass Any
- Known subtypes
-
class DefaultLoggingFilter
Attributes
- Supertypes
-
trait Filtertrait EssentialFilterclass Objecttrait Matchableclass Any
Suppresses Play's startup warning: "Logger configuration in conf files is deprecated and has no effect. Use a logback configuration file instead."
Suppresses Play's startup warning: "Logger configuration in conf files is deprecated and has no effect. Use a logback configuration file instead."
Play emits this (in GuiceApplicationBuilder) whenever it finds log level values under the logger config path, on the assumption that nothing consumes them. On MDTP that assumption is false: LoggerModule reads those same logger.* entries at startup and applies them via Logback's setLevel, so config-driven log levels DO take effect.
This must be a Logback TurboFilter rather than logic in LoggerModule, because the warning is emitted during logger-factory configuration — before module bindings run — so by the time LoggerModule executes the message has already been logged. A TurboFilter is loaded with the Logback config (before the warning fires) and is consulted for every logging event, so it can drop this specific message at source.
Attributes
- Supertypes
-
class TurboFiltertrait LifeCycleclass ContextAwareBasetrait ContextAwareclass Objecttrait Matchableclass AnyShow all