2 * Copyright (c) 2013 Cisco Systems, Inc. and others. All rights reserved.
4 * This program and the accompanying materials are made available under the
5 * terms of the Eclipse Public License v1.0 which accompanies this distribution,
6 * and is available at http://www.eclipse.org/legal/epl-v10.html
8 package org.opendaylight.controller.sal.binding.api;
10 import org.opendaylight.controller.sal.binding.api.BindingAwareBroker.ProviderContext;
14 * A developer implemented component that gets registered with the Broker.
16 * Semantically, a provider may:
19 * <li>Emit Notifications</li>
20 * <li>Provide the implementation of RPCs</li>
21 * <li>Write to the operational data tree</li>
27 * In addition, a BindingAwareProvider can in pursuit of its goals:
30 * <li>Subscribe for Notifications</li>
31 * <li>Invoke RPCs</li>
32 * <li>Read from either the operational or config data tree</li>
33 * <li>Write to the config data tree</li>
35 * (All of the above are things a Consumer can also do).
43 * To get a NotificationService:
47 * public void onSessionInitiated(ProviderContext session) {
48 * NotificationProviderService notificationService = session.getSALService(NotificationProviderService.class);
55 * To register an RPC implementation:
59 * public void onSessionInitiated(ProviderContext session) {
60 * RpcRegistration<MyService> registration = session.addRpcImplementation(MyService.class, myImplementationInstance);
67 * Where MyService.class is a Service interface generated from a yang model with RPCs modeled in it
68 * and myImplementationInstance is an instance of a class that implements MyService.
70 * To register a Routed RPC Implementation:
74 * public void onSessionInitiated(ProviderContext session) {
75 * RoutedRpcRegistration<SalFlowService> flowRegistration = session.addRoutedRpcImplementation(SalFlowService.class, salFlowServiceImplementationInstance);
76 * flowRegistration.registerPath(NodeContext.class, nodeInstanceId);
81 * Where SalFlowService.class is a Service interface generated from a yang model with RPCs modeled
82 * in it and salFlowServiceImplementationInstance is an instance of a class that implements
89 * flowRegistration.registerPath(NodeContext.class, nodeInstanceId);
93 * Is indicating that the RPC implementation is registered to handle RPC invocations that have their
94 * NodeContext pointing to the node with instance id nodeInstanceId. This bears a bit of further
95 * explanation. RoutedRPCs can be 'routed' to an implementation based upon 'context'. 'context' is a
96 * pointer (instanceId) to some place in the data tree. In this example, the 'context' is a pointer
97 * to a Node. In this way, a provider can register its ability to provide a service for a particular
98 * Node, but not *all* Nodes. The Broker routes the RPC by 'context' to the correct implementation,
99 * without the caller having to do extra work. Because of this when a RoutedRPC is registered, it
100 * needs to also be able to indicate for which 'contexts' it is providing an implementation.
102 * An example of a Routed RPC would be an updateFlow(node, flow) that would be routed based on node
103 * to the provider which had registered to provide it *for that node*.
107 * To get a DataBroker to allow access to the data tree:
111 * public void onSessionInitiated(final ProviderContext session) {
112 * DataBroker databroker = session.getSALService(BindingDataBroker.class);
119 public interface BindingAwareProvider {
122 * Callback signaling initialization of the consumer session to the SAL.
124 * The consumer MUST use the session for all communication with SAL or retrieving SAL
125 * infrastructure services.
127 * This method is invoked by {@link BindingAwareBroker#registerProvider(BindingAwareProvider)}
129 * @param session Unique session between consumer and SAL.
131 void onSessionInitiated(ProviderContext session);