This document was generated from CDN thread
Created by: Stephan Steiner on 27-09-2013 07:12:19 AM
Hi
I'm a bit puzzled as to why in selectCmDevice we have <ns1:CmNodes><ns1:CmNode> (followed by the node) and the same structure for devices <ns1:CmDevices><ns1:CmDevice> (followed by the device) but then in SelectCmDevicesSIP we have <ns1:CmNodes><ns1:CmNodeSIP> (why SIP?), but more importantly <ns1:CmDevices><ns1:item> (phone goes here).... so wait... CmNodeSIP but not CmDeviceSIP? But... the complex type is called CmDeviceSIP. And even more puzzling... we're back to <ns1:item> for a device... that's the syntax that more or less is used in RPC encoding.
To make matters even more puzzling.. SelectCtiDevice in literal format returns
<ns1:CtiNodes><ns1:item> (again with the item), and then <ns1:CtiItems><ns1:item>...
So now we have three different formats...
Where is the consistency?
Oh, and let's raise the fun level a notch, shall we... RCP encoded format for SelectCtiDevice holds nodes as follows <CmNodes><item>... the same syntax as RPC encoded selectCmDevice.... no more CmNodeSIP.
Subject: RE: doc/literal format
Replied by: David Staudt on 02-10-2013 04:01:12 PM
Thanks for the comments - I can't point to any particular rationale for all this, but will pass on...
