Minor review fixes
This commit is contained in:
parent
0f410b1252
commit
3846b63dcf
2 changed files with 6 additions and 5 deletions
|
|
@ -17,10 +17,13 @@ akka {
|
|||
# this level is used by the configured loggers (see "event-handlers") as soon
|
||||
# as they have been started; before that, see "stdout-loglevel"
|
||||
stdout-loglevel = "INFO" # Loglevel for the very basic logger activated during AkkaApplication startup
|
||||
# FIXME: Is there any sensible reason why we have 2 different log levels?
|
||||
|
||||
logConfigOnStart = off # Log the configuration when system is starting
|
||||
logConfigOnStart = off # Log the complete configuration at INFO level when the actor system is started.
|
||||
# This is useful when you are uncertain of what configuration is used.
|
||||
|
||||
extensions = [] # list FQCN of extensions which shall be loaded at actor system startup
|
||||
extensions = [] # List FQCN of extensions which shall be loaded at actor system startup.
|
||||
# FIXME: clarify "extensions" here, "Akka Extensions (<link to docs>)"
|
||||
|
||||
# These boot classes are loaded (and created) automatically when the Akka Microkernel boots up
|
||||
# Can be used to bootstrap your application(s)
|
||||
|
|
|
|||
|
|
@ -289,9 +289,7 @@ class ActorSystemImpl(val name: String, val applicationConfig: Config) extends A
|
|||
|
||||
val settings = new Settings(applicationConfig)
|
||||
|
||||
def logConfiguration(): Unit = {
|
||||
log.info(settings.toString)
|
||||
}
|
||||
def logConfiguration(): Unit = log.info(settings.toString)
|
||||
|
||||
protected def systemImpl = this
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue