[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: HTTPAPI, SOAP, and parsing the returned XML

I don't follow what you're saying.  What's missing?  it appears valid to 
me...  Here's the XML you provided:

<ADStart>
   <error code="0" text="NO_ERROR" />
   <ticket>fe81cb7e-fd9e-411b-b3fd-b9c5729728f7</ticket>
</ADStart>

What tags are you saying that you're missing?  It appears to be 
well-formed.   You should be getting the following responses in your 
'Incoming' procedure:

1:   path=/ADStart, name='error', value='', attr(1)='code', attr(2)='0', 
attr(3)='text', attr(4)='NO_ERROR'
2:   path=/ADStart, name='ticket' 
value='fe81cb7e-fd9e-411b-b3fd-b9c5729728f7'
3:   path=/, name='ADStart', value=''

Glenn R. McClenny wrote:
> No, the XML files isn't encoded like that.  It shows the > and < signs, not
> &lt; and &gt;  I figured it was just the missing XML tags around that <error
> code...> line.
>
>   

-----------------------------------------------------------------------
This is the FTPAPI mailing list.  To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------