Regarding 2: I'm not sure why the ServiceValueResolver is throwing an exception in that case, wouldn't use that on action arguments to be honest. Could it be that the typehint can be autowired to something and that causes the exception? Personally would ditch action injection because stateless and stateful mixed is a pain. I prefer to keep my stateless (services) in the constructor arguments of services.

Regarding 3: You can throw exceptions in a resolver. If you ask me, the resolver is the correct place to fetch those objects.

Anyway is it possible to change the order inside the HttpKernel?

I don't think that would make any sense.

Regarding 3: You can throw exceptions in a resolver. If you ask me, the resolver is the correct place to fetch those objects.

One other thing is that on the Resolver I do not have also the controller instance.. which is quite important for my logic...

Personally would ditch action injection because stateless and stateful mixed is a pain. I prefer to keep my stateless (services) in the constructor arguments of services

Well yes.. my services are injected through the constructor.. but there are some services that need the request in order to be generated... (It's a quite complex domain).. But I can not reach to ControllerArguments... maybe I should remove the ServiceArgumentResolver with a CompilerPass..

You can throw exceptions in a resolver. If you ask me, the resolver is the correct place to fetch those objects.

Yes if you throw exception then you break the chain.. and there might be another ArgumentResolver that actually supports this.

One other thing is that on the Resolver I do not have also the controller instance.. which is quite important for my logic...

What do you need the controller instance for? You can get the configured controller from the request $request->attributes->get('_controller') from the top of my head.

maybe I should remove the ServiceArgumentResolver with a CompilerPass

If you don't tag your controller with the tag and make it public yourself, you won't have the ServiceArgumentResolver pass through it.

Yes if you throw exception then you break the chain.. and there might be another ArgumentResolver that actually supports this.

Supports could return false, but perhaps this isn't the right place to do it then? If you need a very complex structure for this, you could also do it in your controller instead.

Thank you for this issue.
There has not been a lot of activity here for a while. Has this been resolved?

Friendly ping? Should this still be open? I will close if I don't hear anything.