Convert toaster to mdsal APIs

[controller.git] / opendaylight / md-sal / samples / toaster-provider / src / main / resources / org / opendaylight / blueprint / toaster-provider.xml

diff --git a/opendaylight/md-sal/samples/toaster-provider/src/main/resources/org/opendaylight/blueprint/toaster-provider.xml b/opendaylight/md-sal/samples/toaster-provider/src/main/resources/org/opendaylight/blueprint/toaster-provider.xml
index 4a2be5d256a328bfcada788c9a49b71ef90f9934..4c7af5b6355813871d17839a1b1b19ef75abe120 100644 (file)
--- a/opendaylight/md-sal/samples/toaster-provider/src/main/resources/org/opendaylight/blueprint/toaster-provider.xml
+++ b/opendaylight/md-sal/samples/toaster-provider/src/main/resources/org/opendaylight/blueprint/toaster-provider.xml
@@ -46,14 +46,14 @@
        via the cfg file. In this manner the toaster can be configured to use the default clustered DataBroker
        or the specialized "pingpong" DataBroker (or any other DataBroker implementation).
    -->
-  <reference id="dataBroker" interface="org.opendaylight.controller.md.sal.binding.api.DataBroker" odl:type="${databroker-type}" />
-  <reference id="notificationService" interface="org.opendaylight.controller.md.sal.binding.api.NotificationPublishService"/>
+  <reference id="dataBroker" interface="org.opendaylight.mdsal.binding.api.DataBroker" odl:type="${databroker-type}" />
+  <reference id="notificationService" interface="org.opendaylight.mdsal.binding.api.NotificationPublishService"/>
 
   <!-- Create the OpendaylightToaster instance and inject its dependencies -->
   <bean id="toaster" class="org.opendaylight.controller.sample.toaster.provider.OpendaylightToaster"
-          init-method="register" destroy-method="unregister">
+          init-method="init" destroy-method="close">
     <argument ref="toasterAppConfig"/>
-    <property name="dataProvider" ref="dataBroker"/>
+    <property name="dataBroker" ref="dataBroker"/>
     <property name="notificationProvider" ref="notificationService"/>
   </bean>
 
@@ -61,4 +61,4 @@
        element automatically figures out the RpcService interface although it can be explicitly specified.
    -->
   <odl:rpc-implementation ref="toaster"/>
-</blueprint>
\ No newline at end of file
+</blueprint>