All Known Subinterfaces:

ActionProviderService, ActionService, BindingAwareBroker.ConsumerContext, BindingAwareBroker.ProviderContext, BindingService, DataBroker, DataTreeChangeService, MountPointService, NotificationProviderService, NotificationPublishService, NotificationService, NotificationService, RpcConsumerRegistry, RpcProviderRegistry

All Known Implementing Classes:

AbstractBindingSalConsumerInstance, AbstractBindingSalProviderInstance, BindingDOMDataBrokerAdapter, BindingDOMMountPointServiceAdapter, BindingDOMNotificationPublishServiceAdapter, BindingDOMNotificationServiceAdapter, BindingDOMRpcServiceAdapter, ForwardingDataBroker, HeliumNotificationProviderServiceAdapter, HeliumNotificationProviderServiceWithInterestListeners, HeliumNotificationServiceAdapter, HeliumRpcProviderRegistry, RootBindingAwareBroker, RootBindingAwareBroker.RootSalInstance
```
@Deprecated(forRemoval=true)
public interface BindingAwareService
```
Deprecated, for removal: This API element is subject to removal in a future version.
Use BindingService instead.

Session-specific instance of the broker functionality.
BindingAwareService is marker interface for infrastructure services provided by the SAL. These services are session-specific, each BindingAwareConsumer and BindingAwareProvider usually has own instance of the service with it's own context.
The consumer's (or provider's) instance of specific service could be obtained by invoking BindingAwareBroker.ConsumerContext.getSALService(Class) method on session assigned to the consumer.
BindingAwareBroker.ConsumerContext and BindingAwareProvider may seem similar, but provider provides YANG model-based functionality and BindingAwareProvider exposes the necessary supporting functionality to implement specific functionality of YANG and to reuse it in the development of BindingAwareConsumers and BindingAwareProviders.

Interface BindingAwareService