Latest post Mon, Apr 10 2017 8:42 AM by olenad. 3 replies.
Page 1 of 1 (4 items)
Sort Posts: Previous Next
  • Thu, Apr 6 2017 10:39 PM

    inews 3.6 to 3.7 server upgrade and soap response minor change

    We have performed the 3.6 to 3.7  upgrade of a test system at a customer site. There is an in-house application developed by the company that uses web services.

    The developer reports that the SOAP response, after the upgrade, changed a little bit. The tags shown below come from the system after the iNEWS server upgrade from 3.6 to 3.7. They have “<ns2:”, while before the upgrade, the response used to come with “<ns3:”, instead.

     Is it normal ?

    <ns2:QueueLocator>129959042.6820247.3</ns2:QueueLocator>

    <ns2:StoryAsNSML>&lt;?xml version="1.0" encoding="UTF-8"?>&lt;nsml:nsml xmlns:nsml="http://avid.com/nsml" version="3.1">&lt;head>&lt;meta break="1" float="false" hold="false" mcserror="false" rate="140" wordlength="6"/>&lt;rgroup number="10"/>&lt;wgroup number="182"/>&lt;formname>JORNAIS/BDRJ/INDICAD&lt;/formname>&lt;storyid>07bf0482:0070c7d2:582c19a7&lt;/storyid>&lt;/head>&lt;fields>&lt;string aready="false" bg="0" id="page-number" ro="false" uec="false" urgency="1">   &lt;/string>&lt;string aready="false" bg="0" id="var-1" ro="false" uec="false" urgency="1"> *   BDRJ&lt;/string>&lt;string aready="false" bg="0" id="var-2" ro="false" uec="false" urgency="1"/>&lt;string aready="false" bg="0" id="title" ro="false" uec="false" urgency="1">xxªFEIRA, xx / xx / 2016&lt;/string>&lt;string aready="false" bg="0" id="var-4" ro="false" uec="false" urgency="1"/>&lt;string aready="false" bg="0" id="presenter" ro="false" uec="false" urgency="1"/>&lt;duration aready="false" bg="0" id="audio-time" ro="false" uec="false" urgency="1">0&lt;/duration>&lt;duration aready="false" bg="0" id="tape-time" ro="false" uec="false" urgency="1">0&lt;/duration>&lt;duration aready="false" bg="0" id="total-time" ro="false" uec="false" urgency="1">0&lt;/duration>&lt;string aready="false" bg="0" id="video-id" ro="false" uec="false" urgency="1"> &lt;/string>&lt;string aready="false" bg="0" id="modify-by" ro="false" uec="false" urgency="1">maia&lt;/string>&lt;string aready="false" bg="0" id="endorse-by" ro="false" uec="false" urgency="1"/>&lt;string aready="false" bg="0" id="cume-time" ro="false" uec="1" urgency="1">@21603&lt;/string>&lt;string aready="false" bg="0" id="ready" ro="false" uec="false" urgency="1">OK&lt;/string>&lt;string aready="false" bg="0" id="writer" ro="false" uec="false" urgency="1"> &lt;/string>&lt;date aready="false" bg="0" id="modify-date" ro="false" uec="false" urgency="1">1479283148&lt;/date>&lt;string aready="false" bg="0" id="var-21" ro="false" uec="false" urgency="1"/>&lt;string aready="false" bg="0" id="var-5" ro="false" uec="false" urgency="1"/>&lt;string aready="false" bg="0" id="var-6" ro="false" uec="false" urgency="1"/>&lt;string aready="false" bg="0" id="var-7" ro="false" uec="false" urgency="1"/>&lt;string aready="false" bg="0" id="var-3" ro="false" uec="false" urgency="1"/>&lt;/fields>&lt;body family="0" findent="0" font="" pindent="0" pitch="0" rindent="0" tabs="24">&lt;p family="0" font="" pitch="0">&lt;a idref="0"/>&lt;/p>&lt;p family="0" font="" pitch="0"/>&lt;p family="0" font="" pitch="0">&lt;a idref="1"/>&lt;pi>{{//// SOBE SOM ////&lt;/pi>&lt;/p>&lt;p family="0" font="" pitch="0"/>&lt;p family="0" font="" pitch="0"/>&lt;p family="0" font="" pitch="0">&lt;pi>DEIXA :             &lt;/pi>&lt;/p>&lt;p family="0" font="" pitch="0">&lt;pi>}}&lt;/pi>&lt;/p>&lt;/body>&lt;aeset family="0" font="" pitch="0">&lt;ae family="0" font="" id="0" pitch="0" runs="0" type="G" version="S2.1">&lt;ap family="0" font="" pitch="0">&lt;i family="0" font="" pitch="0">LOCUTOR VIVO&lt;/i>&lt;/ap>&lt;/ae>&lt;ae family="0" font="" id="1" pitch="0" runs="0" type="G" version="S2.1">&lt;ap family="0" font="" pitch="0">&lt;i family="0" font="" pitch="0">//// RODA VT ////&lt;/i>&lt;/ap>&lt;/ae>&lt;/aeset>&lt;/nsml:nsml></ns2:StoryAsNSML>

     

    </Stories

  • Fri, Apr 7 2017 9:19 AM In reply to

    • olenad
    • Not Ranked
    • Joined on Thu, Nov 6 2014
    • Posts 22
    • Points 235

    Re: inews 3.6 to 3.7 server upgrade and soap response minor change

    Hi,

     

    yep, that's correct

     

    Thanks,

    Olena

  • Fri, Apr 7 2017 2:13 PM In reply to

    Re: inews 3.6 to 3.7 server upgrade and soap response minor change

    The developer said that in this case he would need to change the system´s source code in order to support the different response.

    Is there any way of making iNEWS 3.7 respond exactly the same way as 3.6 ?

    Thanks in advance!

  • Mon, Apr 10 2017 8:42 AM In reply to

    • olenad
    • Not Ranked
    • Joined on Thu, Nov 6 2014
    • Posts 22
    • Points 235

    Re: inews 3.6 to 3.7 server upgrade and soap response minor change

    Hi, 

    <ns2: ...> or <ns3:..> are auto-generated namespace names 

    we cannot garantee some specific name in response because it's genereted by framework

     

    You may look into this line in "GetStories" response, for example, to check what name space you should use

    Here is example from my LAB 

    <GetStoriesResponse xmlns="http://avid.com/inewsqueue/types" xmlns:ns2="http://avid.com/inewssystem/types" xmlns:ns3="http://avid.com/inewsstory/types">

    Olena

     

Page 1 of 1 (4 items)

© Copyright 2011 Avid Technology, Inc.  Terms of Use |  Privacy Policy |  Site Map |  Find a Reseller