#573
  • Created on
    2010-12-08 16:42
  • Reported by
    clintgilbert
  • Status
    Fixed
  • Priority
    Normal (3)
  • Assigned to
    viktorklang
  • Milestone
    1.2
  • Plan Level
    -
  • Due Date
    -

Attachments

Related Tickets

Add new subtask or bug

Akka should warn the user if required elements of akka.conf are missing

I recently spent a little time chasing an issue related to an akka.conf that looked like this:

remote {
  server {
    require-cookie = off
  }
}

Changing it to this fixed it:
akka {
  remote {
    server {
      require-cookie = off
    }
  }
}

Since it seems that the enclosing akka {... } expression is required, it would be nice if Akka could warn the user when it is missing.

On akka-user, Viktor Klang said:
"I don't think that'd help if you import the defaults from another conf."

Perhaps some very simple validation could be performed after any defaults are merged in? I'm sure that's terribly naive, as akka.conf looks very DSL-ish, and I don't know what implications that would have.
User picture
  on 2010-12-10 07:19 *
By Jonas Bonér
Milestone set to 1.0
User picture
  on 2010-12-22 00:53 *
By Jonas Bonér
Milestone changed from 1.0 to 1.1
Will be a lot of work since need to basically create a parser for the config and check it by hand by recursively look entries up in the ConfigMap.
User picture
  on 2011-02-23 09:25 *
By Jonas Bonér
Milestone changed from 1.1 to 1.2
Updating tickets (#87, #439, #461, #470, #503, #520, #521, #552, #560, #572, #573, #578, #592, #599, #611, #619, #621, #630, #637, #639, #641, #642, #644, #653, #655, #657, #665, #670, #455, #487, #601)
User picture
  on 2011-05-12 09:35 *
By viktorklang
Assigned to set to viktorklang
Status changed from New to Fixed
Fixed in: https://github.com/jboner/akka/commit/53cf5079fdfd44ba487b87659e51bf310c2c818b

If System property: ''akka.output.config.source" is non-null, then Akka will print to System.out where it loads it's config from, and whenever it uses a default value in the config.