Spring shorthand, again

[Nate Klingenstein]

> It’s apparent that the connection is failing and why, but it’s not apparent where the configuration even comes from or how to begin resolving it, which is why I couldn’t think of an elegant way to log it without making some presumptions about it.

(this being, of course, dependent on exactly how you break it and whether you understand how Spring works and everything is wired together — you’ll of course get parsing errors sometimes, and that’s where things got tangled here.

I’m not totally sure what gets logged if the configuration is syntactically valid, other than “they couldn’t find it after days of looking” and “I had to ask about it to understand it", which is why I thought to ask about it again.)