XML API Syntax

[phillip.isley]

Good morning,

Using the latest schema (10-0-0_SP4) provided on your website, I was able to create class files representing the ep service. All of this is working as expected. The problem I am having is related to the xsi:type string your schema is creating.

Below is the result (other than omitting my account info) when serializing based on your schema.

<?xml version='1.0' encoding='utf-8'?>
<serv:message
  xmlns:history='http://www.webex.com/schemas/2002/06/service/history'
  xmlns:com='http://www.webex.com/schemas/2002/06/common'
  xmlns:att='http://www.webex.com/schemas/2002/06/service/attendee'
  xmlns:meet='http://www.webex.com/schemas/2002/06/service/meeting'
  xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'
  xmlns:use='http://www.webex.com/schemas/2002/06/service/user'
  xmlns:xsd='http://www.w3.org/2001/XMLSchema'
  xmlns:ep='http://www.webex.com/schemas/2002/06/service/ep'
  xmlns:serv='http://www.webex.com/schemas/2002/06/service'>
  <serv:header>
  <serv:securityContext>
  <com:webExID>myid</com:webExID>
  <com:password>mypassword</com:password>
  <com:siteID>mysiteid</com:siteID>
  <com:partnerID>mypartnerid</com:partnerID>
  </serv:securityContext>
  </serv:header>
  <serv:body>
  <serv:bodyContent xsi:type='ep:lstRecording'>
  <ep:listControl>
  <ep:startFrom>1</ep:startFrom>
  <ep:maximumNum>3</ep:maximumNum>
  </ep:listControl>
  <ep:createTimeScope>
  <ep:createTimeStart>06/16/2016 00:00:01</ep:createTimeStart>
  <ep:createTimeEnd>06/16/2016 23:59:59</ep:createTimeEnd>
  </ep:createTimeScope>
  <ep:returnSessionDetails>true</ep:returnSessionDetails>
  </serv:bodyContent>
  </serv:body>
</serv:message>

When posting this XML, the server responds with a status OK, but index out of range error. I determined that it did not like the

xsi:type='ep:lstRecording'

If I manually adjust the XML before submitting to

xsi:type='java:com.webex.service.binding.ep.LstRecording'

then my response is correct and everything is able to be deserialized.

Is this the expected behavior? I believe I read in another string that the server should accept values like "ep:lstRecording", "history:LstrecordaccessHistory", etc. If this is not the case, than the provided schema is not correctly creating the xsi:type.

[phillip.isley]

Are Cisco employees actually monitoring the threads in this forum or is it solely the community of customers? I was really hoping to hear a response by now given that it's simply about the syntax of the provided API.

[kasutton · Accepted solution]

Hi Phillip,

Sorry for the delay. We do monitor these forums, though our priority is requests that come directly to us via email or our case tracking system which originate from our Technical Support team. These forums mostly exist for users to get free support from other users, but we engage as time allows. As such, there is no SLA for responses on forum replies. If you have the Gold Developer Program (this is a paid program), you have direct access to us via email, which would usually yield much quicker results (normally well inside 24 hour turnaround time, save for weekends).

To answer your question, we really recommend using the verbose form, but it will work with the truncated ep.LstRecording if you enclose it with a double quotation instead of single.

So, instead of:

  <serv:bodyContent xsi:type='ep:lstRecording'>

Try:

  <serv:bodyContent xsi:type="ep:lstRecording">

Hope this helps,

Kasey