1 ===============================================
2 Model-Driven Service Abstraction Layer (MD-SAL)
3 ===============================================
8 MD-SAL provides infrastructure for binding YANG models to Java object model and infrastructure
9 for providing YANG-defined interaction patterns:
10 * Reactive datastore update
11 * RPC and Action invocation
12 * Notification sourcing and delivery
14 Behavior/Feature Changes
15 ========================
16 The Binding mapping of ``type bits`` YANG statement has been updated to use a dedicated common
17 superinterface, ``BitsTypeObject``. Furthermore individual bits within these classes are now represented
18 as primitive ``boolean`` values rather than nullable ``Boolean`` objects.
22 Both ``DOMRpcProviderService`` and ``RpcProviderService`` have gained the ability to register single-type
23 and flexible multi-type RPC implementations. ``RpcConsumerRegistry`` have gained the ability to access single-RPC
24 handles. These capabilities are based on new codegen feature, which generates ``@FunctionalInterface`` interfaces
25 for each individual ``rpc``, similar to how ``action`` statements are processed.
27 Binding code generator now recognizes ``RFC8040 rc:yang-data`` extensions and generates corresponding interfaces.
31 ``NotificationService.registerNotificationListener()`` method has been deprecated, along with its Binding
32 specification interfaces based on ``NotificationListener``. These will be removed in a future major release.
34 ``RpcProviderService.registerRpcImplementation()`` methods, ``RpcConsumerRegistry.getRpcService()`` methods and
35 Binding specification interfaces based on ``RpcService`` have been deprecated. These will be removed in a future
44 The following table lists the issues resolved in this release.
46 .. jira_fixed_issues::
48 :versions: 12.0.0-12.0.0
52 The following table lists the known issues that exist in this release.
54 .. jira_known_issues::
56 :versions: 12.0.0-12.0.0