I have to mess around with time schedules, so I implemented TodAccess and TimeSchedule. And for my todAccess assigned to a dual mode device, I get this when I extract it
<?xml version='1.0' encoding='utf-8'?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Body><ns:getTodAccessResponse xmlns:ns="http://www.cisco.com/AXL/API/11.5"><return><todAccess uuid="{92C77E77-BF1A-4E49-B255-2D1B50897754}"><name>TOD-RD-5e5b0fe9-0c04-a43e-aec7-0d919014dd02</name><description>00767770351</description><ownerIdName uuid="{8E6DFF7B-D81F-AD9E-4F2B-26A51F19D262}">ap5user1</ownerIdName><members><member uuid="{95E58294-9344-4E27-A399-6A0C900F39EF}"><timeScheduleName uuid="{2E437DBA-9FF7-CB95-5A70-52483D3B54C1}">TS-RD-5e5b0fe9-0c04-a43e-aec7-0d919014dd02</timeScheduleName><accessListName/></member></members><associatedRemoteDestination><remoteDestination/></associatedRemoteDestination></todAccess></return></ns:getTodAccessResponse></soapenv:Body></soapenv:Envelope>
Note the contents of <associatedRemoteDestination>.. it contains one empty remoteDestination element. Is that really correct?
For an RD associated to a remote destination profile, there's some content to the remoteDestination tag as I would expect it.
<?xml version='1.0' encoding='utf-8'?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Body><ns:getTodAccessResponse xmlns:ns="http://www.cisco.com/AXL/API/11.5"><return><todAccess uuid="{2F371609-1E8B-0A4F-FE92-288C6F3963B6}"><name>TOD-RD-5ca7bfa3-2800-84dc-6f44-6175a646ea68</name><description>00761234567</description><ownerIdName uuid="{C4781531-2DF4-8153-35E8-9B61AEFC9FBB}">testuser</ownerIdName><members><member uuid="{64F47ABA-C322-4112-9126-F14B84A23A8E}"><timeScheduleName /><accessListName/></member></members><associatedRemoteDestination><remoteDestination>RD_Templäte2</remoteDestination></associatedRemoteDestination></todAccess></return></ns:getTodAccessResponse></soapenv:Body></soapenv:Envelope>
The schema says that there are 0-infinity of remoteDestination. So wouldn't the first case be one where there's none? Imagine somebody parsing, and then trying to extract the Remote Destination. "So.. there is a remote destination, let's load it, but hey, wait, it is empty? WTF".
