Implement DOMDataTreeChangeListener.onInitialData
[controller.git] / opendaylight / md-sal / samples / toaster-consumer / src / main / resources / org / opendaylight / blueprint / toaster-consumer.xml
1 <?xml version="1.0" encoding="UTF-8"?>
2 <blueprint xmlns="http://www.osgi.org/xmlns/blueprint/v1.0.0"
3            xmlns:odl="http://opendaylight.org/xmlns/blueprint/v1.0.0"
4     odl:use-default-for-reference-types="true">
5
6   <!-- Retrieves the RPC service for the ToasterService interface -->
7   <odl:rpc-service id="toasterService" interface="org.opendaylight.yang.gen.v1.http.netconfcentral.org.ns.toaster.rev091120.ToasterService"/>
8
9   <!-- Create the KitchenServiceImpl instance and inject the RPC service identified by "toasterService" -->
10   <bean id="kitchenService" class="org.opendaylight.controller.sample.kitchen.impl.KitchenServiceImpl"
11           init-method="register" destroy-method="unregister">
12     <argument ref="toasterService"/>
13   </bean>
14
15   <!-- Register the KitchenServiceImpl to receive yang notifications -->
16   <odl:notification-listener ref="kitchenService"/>
17
18   <!-- Advertise the KitchenServiceImpl with the OSGi registry with the type property set to "default" . The
19        type property is optional but can be used to distinguish this implementation from any other potential
20        KitchenService implementations (if there were any). Clients consuming the KitchenService can pick the
21        desired implementation via the particular type.
22   -->
23   <service ref="kitchenService" interface="org.opendaylight.controller.sample.kitchen.api.KitchenService"
24           odl:type="default"/>
25 </blueprint>