Bug fix for retrieval of nr-operating-bands node

Issue-ID: AAI-4207
Change-Id: Ia2564568939f618d637eb17bc6ac636852005369
Signed-off-by: akshay.khairnar@t-systems.com <akshay.khairnar@t-systems.com>

diff --git a/aai-schema/src/main/resources/onap/oxm/v31/aai_oxm_v31.xml b/aai-schema/src/main/resources/onap/oxm/v31/aai_oxm_v31.xml
index 8657eff..401c4eb 100644 (file)
--- a/aai-schema/src/main/resources/onap/oxm/v31/aai_oxm_v31.xml
+++ b/aai-schema/src/main/resources/onap/oxm/v31/aai_oxm_v31.xml
@@ -16175,7 +16175,7 @@
                         <xml-property name="description" value="Specifies the maximum packet size supported by the network slice or the network slice subnet in downlink."/>
                     </xml-properties>
                 </xml-element>
-                               <xml-element java-attribute="nROperatingBands" name="nr-operating-bands" type="inventory.aai.onap.org.v31.NrOperatingBands">
+                               <xml-element java-attribute="nrOperatingBands" name="nr-operating-bands" type="inventory.aai.onap.org.v31.NrOperatingBands">
                     <xml-properties>
                         <xml-property name="description" value="Represents which 5G NR frequency bands can be used to access the network slice."/>
                     </xml-properties>