aboutsummaryrefslogtreecommitdiffstats
path: root/generic-resource-api/provider/src/main/resources/initial/generic-resource-api-provider.xml
blob: a9d3e639b7fe5e9da99d6da0c6aba1bd0200b50b (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
<?xml version="1.0" encoding="UTF-8"?>
<!-- vi: set et smarttab sw=4 tabstop=4: -->
<snapshot>
    <configuration>
        <data xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
            <modules xmlns="urn:opendaylight:params:xml:ns:yang:controller:config">
                <module>

                    <!-- This xmlns:prefix should match the namespace in the *-provider-impl.yang file
                         The prefix: inside type should match the prefix of the yang file. -->
                    <type xmlns:prefix="org:onap:sdnc:northbound:GENERIC-RESOURCE-API:provider:impl">
                        prefix:GENERIC-RESOURCE-API-provider-impl
                    </type>
                    <name>GENERIC-RESOURCE-API-provider-impl</name>

                    <!--  The following sections contain bindings to services defined in the
                          *-provider-impl yang file. For example the rpc-registry is required
                          because we have a dependency (or augmentation) named "rpc-registry"
                          and which binds to the md-sa-binding-registry. If you remove those
                          dependencies from the yang file then you can remove them from here. -->
                    <rpc-registry>
                        <type xmlns:binding="urn:opendaylight:params:xml:ns:yang:controller:md:sal:binding">binding:binding-rpc-registry</type>
                        <name>binding-rpc-broker</name>
                    </rpc-registry>

                    <data-broker>
                        <type xmlns:binding="urn:opendaylight:params:xml:ns:yang:controller:md:sal:binding">binding:binding-async-data-broker</type>
                        <name>binding-data-broker</name>
                    </data-broker>

                     <notification-service>
                        <type xmlns:binding="urn:opendaylight:params:xml:ns:yang:controller:md:sal:binding:impl">
                            binding:binding-new-notification-publish-service
                        </type>
                        <name>binding-notification-broker</name>
                    </notification-service>
                </module>

            </modules>
        </data>

    </configuration>

    <!--  Required capabilities are basically a listing of all modules that need to be imported before
          our service can be resolved. Capabilities for dependencies defined above are implied which is
          why we do not have define a required capability for the data broker, for example. -->
    <required-capabilities>
        <capability>org:onap:sdnc:northbound:GENERIC-RESOURCE-API:provider:impl?module=GENERIC-RESOURCE-API-provider-impl&amp;revision=2017-08-24</capability>
    </required-capabilities>

</snapshot>