I'm starting a new project with what will be a sf 2.3 and I'm getting.
Scope Crossing Injection detected: The definition "fos_rest.request.param_fetcher" references the service "fos_rest.request.param_fetcher.reader" which belongs to another scope hierarchy. This service might not be available consistently. Generally, it is safer to either move the definition "fos_rest.request.param_fetcher" to scope "container", or declare "request" as a child scope of "container". If you can be sure that the other scope is always active, you can set the reference to strict=false to get rid of this error.
IMO, we could add strict=false to this definition, but I'm not sure as I don't know the bundle that well.
This looks like a bug in Symfony. The container scope should be considered as parent of any scope.
So, is there a way to make it work with the current Symfony 2.3 branch ?
the issue hasnt been solved in core yet? /cc @fabpot
That's because the request scope is now created by the ContainerAwareHttpKernel instead of FrameworkBundle. So, at the time the compilation occurs, the request scope does not exist yet. See symfony/symfony@550df5a
see symfony/symfony@853f681 for the fix.
I've checked and this issue is now gone.
yes, thank you