There's nothing the content service would do to recover (note that a throw here would mean an unexpected error, 404s and such would NOT throw), thus the content service has no reason to catch the exception. Returning "null" is a possible recovery, but I'm not sure it's what we'd want here, since I don't think it should be the job of services to trap and record errors, that's a job for the application logic.