Faulty XML deserialization

Bug #795149 reported by Salvatore Orlando
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Network Service (Old)
Salvatore Orlando

Bug Description

Deserialization of XML responses does not work well with lists:

For instance:
    <network id="047"/>
    <network id="045"/>
    <network id="044"/>
    <network id="043"/>
    <network id="002"/>
    <network id="001"/>
    <network id="026"/>
    <network id="021"/>
    <network id="020"/>
    <network id="023"/>
    <network id="022"/>
    <network id="033"/>
    <network id="046"/>
    <network id="009"/>
    <network id="008"/>
    <network id="029"/>
    <network id="028"/>
    <network id="041"/>
    <network id="040"/>
    <network id="024"/>
    <network id="027"/>
    <network id="007"/>
    <network id="006"/>

When deserialized, is transformed into the following dictionary:

{u'networks': {u'network': {u'id': u'006'}}}

Changed in network-service:
status: New → Confirmed
assignee: nobody → Salvatore Orlando (salvatore-orlando)
Changed in network-service:
status: Confirmed → In Progress
Changed in network-service:
status: In Progress → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers