cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
587
Views
2
Helpful
2
Replies

LLbmHubGroup schema does not match RLbmHubGroup

Jonathan Els
Level 5
Level 5

Hi,

The LLbmHubGroup schema is the following:

<xsd:complexType name="LLbmHubGroup">
  <xsd:sequence minOccurs="0">
  <xsd:element maxOccurs="1" minOccurs="0" name="name" type="xsd:string"/>
  <xsd:element maxOccurs="1" minOccurs="0" name="description" type="xsd:string"/>
  <xsd:element maxOccurs="1" minOccurs="0" name="member1" type="xsd:string"/>
  <xsd:element maxOccurs="1" minOccurs="0" name="member2" type="xsd:string"/>
  <xsd:element maxOccurs="1" minOccurs="0" name="member3" type="xsd:string"/>
  </xsd:sequence>
  <xsd:attribute name="uuid" type="axlapi:XUUID"/>
</xsd:complexType>

We can compare this to the RLbmHubGroup schema:

<xsd:complexType name="RLbmHubGroup">
  <xsd:sequence minOccurs="0">
  <xsd:element maxOccurs="1" minOccurs="0" name="name" type="xsd:string"/>
  <xsd:element maxOccurs="1" minOccurs="0" name="description" type="xsd:string"/>
  <xsd:element maxOccurs="1" minOccurs="0" name="member1" type="xsd:string"/>
  <xsd:element maxOccurs="1" minOccurs="0" name="member2" type="xsd:string"/>
  <xsd:element maxOccurs="1" minOccurs="0" name="member3" type="xsd:string"/>
  <xsd:element maxOccurs="1" minOccurs="0" name="members">
  <xsd:complexType>
  <xsd:sequence minOccurs="0">
  <xsd:element maxOccurs="unbounded" minOccurs="0" name="member" type="axlapi:RProcessNodes"/>
  </xsd:sequence>
  </xsd:complexType>
  </xsd:element>
  </xsd:sequence>
  <xsd:attribute name="uuid" type="axlapi:XUUID"/>
</xsd:complexType>

For some reason,  the list response definition just removes the members detail in RProcessNodes

Can anyone explain this to me?  I think this is also a bug?

1 Accepted Solution

Accepted Solutions

Paul Giralt
Cisco Employee
Cisco Employee

I suspect this is a performance optimization when doing the list and if you want the details, you need to query for the specific item.

View solution in original post

2 Replies 2

Paul Giralt
Cisco Employee
Cisco Employee

I suspect this is a performance optimization when doing the list and if you want the details, you need to query for the specific item.

OK, not the answer I wanted, but makes sense...