Because of request listeners requiring the, siteaccess / scoped config errors that were difficult to track have occured, like in EZP-24910, or EZP-24909.

But of course, if one implements a non-lazy request listener having dependencies which requires the SiteAccess (or resolved settings), the problem will occur again.

Either the limitation should be removed, or identifying it should be made MUCH easier.

We might be able to do so in compiler passes:

• tracking down services that depend on the siteaccess
• scan request listeners, and check their dependencies for services found above