Added RefreshPolicies to PolicyService.

chrome/browser/policy/policy_service_stub.cc

Index: chrome/browser/policy/policy_service_stub.cc
diff --git a/chrome/browser/policy/policy_service_stub.cc b/chrome/browser/policy/policy_service_stub.cc
index 0bbfc631982e0895478924dd9ca6892abae846d6..7af694494b5131a9c59ccfc4daf17675255c90b6 100644
--- a/chrome/browser/policy/policy_service_stub.cc
+++ b/chrome/browser/policy/policy_service_stub.cc
@@ -4,6 +4,8 @@
 
 #include "chrome/browser/policy/policy_service_stub.h"
 
+#include "base/message_loop.h"
+
 namespace policy {
 
 PolicyServiceStub::PolicyServiceStub() {}
@@ -28,4 +30,9 @@ bool PolicyServiceStub::IsInitializationComplete() const {
   return true;
 }
 
+void RefreshPolicies(const base::Closure& callback) {
+  if (!callback.is_null())
+    MessageLoop::current()->PostTask(FROM_HERE, callback);

[Mattias Nissler (ping if slow), 2012/04/27 09:03:27]

Any reason to not directly invoke the callback? That may happen if the providers
call back immediately in the full implementation as well.

[Joao da Silva, 2012/04/27 11:24:12]

In this case it doesn't matter. I was concerned with callbacks that call
RefreshPolicies again during their execution; in the main impl it's not a
problem because the vectors are swapped. I only see this potentially happening
in tests.

+}
+
 }  // namespace policy