Create a RegisterViewAssociate method in ViewManager

services/ui/view_manager/view_manager_impl.cc

 // Copyright 2015 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 #include "services/ui/view_manager/view_manager_impl.h"
 
 #include <utility>
 
+#include "base/bind.h"
+
 #include "services/ui/view_manager/view_impl.h"
 #include "services/ui/view_manager/view_tree_impl.h"
 
 namespace view_manager {
 
 ViewManagerImpl::ViewManagerImpl(ViewRegistry* registry)
     : registry_(registry) {}
 
 ViewManagerImpl::~ViewManagerImpl() {}
 
@@ skipping 10 matching lines @@
 void ViewManagerImpl::CreateViewTree(
     mojo::InterfaceRequest<mojo::ui::ViewTree> view_tree_request,
     mojo::InterfaceHandle<mojo::ui::ViewTreeListener> view_tree_listener,
     const mojo::String& label) {
   registry_->CreateViewTree(
       view_tree_request.Pass(),
       mojo::ui::ViewTreeListenerPtr::Create(std::move(view_tree_listener)),
       label);
 }
 
+// this should only really be called by trusted code (ie launcher) -- how to
+// ensure that?
+void ViewManagerImpl::RegisterViewAssociate(
+    mojo::InterfaceHandle<mojo::ui::ViewAssociate> view_associate,
+    const mojo::String& url) {
+  registry_->RegisterViewAssociate(
+      registry_, mojo::ui::ViewAssociatePtr::Create(std::move(view_associate)),
+      url,  // should we really be passing this in like this?
+      base::Bind(&ViewManagerImpl::OnAssociateConnectionError,
+                 base::Unretained(this)));
+}
+
+// copied from ViewManagerImpl, is this a bad idea?
+void ViewManagerImpl::OnAssociateConnectionError(const std::string& url) {
+  LOG(ERROR) << "Exiting due to view associate connection error: url=" << url;
+  // Shutdown();
+}
+
 }  // namespace view_manager