FriendsOfSymfony/FOSRestBundle — pull request #743 by mnapoli (2014-04-12 16:41:04+00:00)
Title: Allow controller as services, even when the service ID is the controller class name

The background behind this issue is here: https://github.com/FriendsOfSymfony/FOSRestBundle/issues/604#issuecomment-40284026

The RestRouteLoader now first check if the resource is a service in the container before checking if it's a class name.

That allows to register controller as services in the container and use them in routes, even when we register them by their class name in the container.

The tests turned out to be a bit messy. I tried to keep it clean, but if you want me to remove it I can. I also confirm that the test was failing before the fix, and is now passing after the change in RestRouteLoader.