Problems with "execute procedure dbreaddevicexml"

Version 1
    This document was generated from CDN thread

    Created by: Florian Kroessbacher on 13-02-2012 05:09:17 AM
    Hy out there,
     
    i have the following problem. I need to get the device XML from the Device.
    we are running CuCM 8.5.
     
    When i do it with the stored procedure i get the "TAGS" with "><" and so on.
    stored_procedure.txt
    Query
    execute procedure dbreaddevicexml ('3c19d1f2-760a-2ae7-63ab-77435d3cc562')
     
    When i run the same query as a sql query to the specific tables the tags come wright with "><"
    devicexml.txt
    Query

    select xml from devicexml4k where fkdevice = 'e88d9282-63fc-84e6-f7aa-b53683c2f3c2' union select xml from devicexml8k where fkdevice = 'e88d9282-63fc-84e6-f7aa-b53683c2f3c2' union select xml from devicexml16k where fkdevice = 'e88d9282-63fc-84e6-f7aa-b53683c2f3c2'

    I attached the CuCM Logs
     
    maybe there is somebode to help me, or should i open a TAC
     

    Subject: RE: Problems with "execute procedure dbreaddevicexml"
    Replied by: David Staudt on 13-02-2012 01:57:54 PM
    To be honest I would prefer the 'escaped' verion of the device XML, as this helps prevent transport/encapsulation issues if the actual XML itself is malformed or has some unexpected characters in it.  It should be easy enough to unescape the response.
     
    I can see where it would be nice to have consistency too    Is that what you are looking for..?
     
     

    Subject: RE: Problems with "execute procedure dbreaddevicexml"
    Replied by: David Staudt on 13-02-2012 02:34:32 PM
    To my knowledge, this is the only time I've seen XML get escaped like this by AXL - not aware of any change to the executeSQLQuery responses, etc.

    Subject: RE: Problems with "execute procedure dbreaddevicexml"
    Replied by: Florian Kroessbacher on 13-02-2012 02:28:58 PM
    To be honest I would prefer the 'escaped' verion of the device XML, as this helps prevent transport/encapsulation issues if the actual XML itself is malformed or has some unexpected characters in it.  It should be easy enough to unescape the response.
     
    I can see where it would be nice to have consistency too    Is that what you are looking for..?
     
     

     
    Hy David,
     
    thnxs for the reply.
    so i see the way is to give back the 'escaped' version. will this be change over the entire executeSql or only for some operations, if there are only some operations,
    is there a list out there which operations ar affected.
    and to unescape shouldn't be the challenge, i think i hadn't checked after i had changed my code :-)
     
    thnxs Floh

    Subject: RE: Problems with "execute procedure dbreaddevicexml"
    Replied by: Florian Kroessbacher on 13-02-2012 03:07:32 PM
    Ok thnxs

    cheers Floh