spurious org.springframework.beans.factory.NoSuchBeanDefinitionException

[Cantor, Scott]

> Given I flagrantly disregard the recommendation to upgrade in place ;),

The fact that it's happening enough to notice when it's never happened to me in a single instance that didn't involve the service reloading stuff (*) is basically virtual proof that an older file has to be there.

Otherwise it would mean Spring were completely broken, whereas the Occam's Razor explanation fully explains it.

I guess I would start by checking for anything in the old system/ folder we used to create.

-- Scott

(*) Spring has a bug involving the use of parent beans across contexts when certain conditions are met, but you have to "create it twice" to see it, and the flows only instantiate once, and there are other caveats unmet in this case.