Change RulesRegistryService to use ProfileKeyedAPI.

chrome/browser/extensions/api/declarative/declarative_api.cc

Index: chrome/browser/extensions/api/declarative/declarative_api.cc
diff --git a/chrome/browser/extensions/api/declarative/declarative_api.cc b/chrome/browser/extensions/api/declarative/declarative_api.cc
index 3963823955a50b9551b5dd87f2526022bf0c2723..842884326bdbfa7c6e9700a8b739f5cc8f23bf20 100644
--- a/chrome/browser/extensions/api/declarative/declarative_api.cc
+++ b/chrome/browser/extensions/api/declarative/declarative_api.cc
@@ -37,8 +37,7 @@ bool RulesFunction::RunImpl() {
   EXTENSION_FUNCTION_VALIDATE(args_->GetString(0, &event_name));
 
   RulesRegistryService* rules_registry_service =
-      ExtensionSystemFactory::GetForProfile(profile())->
-      rules_registry_service();
+      ProfileKeyedAPIFactory<RulesRegistryService>::GetForProfile(profile());

[Devlin, 2013/04/26 01:07:09]

Add a convenience method in RulesRegistryService for these (see
OmniboxAPI::Get(Profile) for an example).

[Patrick Riordan, 2013/04/26 01:44:55]

Done.

   rules_registry_ = rules_registry_service->GetRulesRegistry(event_name);
   // Raw access to this function is not available to extensions, therefore
   // there should never be a request for a nonexisting rules registry.