diLocationsset, but for the time being I got it to work by explicitly setting
diLocations. Perhaps it's because the controller classes in question are in a subsystem? I had to add the controller directory for the subsystem before it worked (which makes sense).
fwas a property into the "client" bean?
for ( s in ["list", "of", "subsystems"] ) setupSubsystem( s );That should solve the lazy-loading under load issue (you may need an application scope lock around that tho').
"hello"so they would fail as well.