[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: XML parse failed at line 1, col 0: no element found
You are welcome. The first web service is always the hardest one.
Thomas.
ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx schrieb am 25.02.2011 13:52:26:
> Von: mr.singhjitender@xxxxxxxxx
> An: ftpapi@xxxxxxxxxxxxxxxxxxxxxx
> Datum: 25.02.2011 14:01
> Betreff: Re: Re: XML parse failed at line 1, col 0: no element found
> Gesendet von: ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
>
> Hi Thomas,
>
> fisr of all thanks a lot for your suggestion.
> Now i am able to get the data in xmldata variable.
>
> Again thanks a lot.
>
>
> Thanks & Regards
> Jitender Singh.
>
> On Thu, Feb 24, 2011 at 6:32 PM, <thomas.raddatz@xxxxxx> wrote:
>
> >
> > First of all lets make clear that the server successfully
replies to
> > your request and that you receive the complete response. Hence
all
> > basic communication problems have been solved. You entered the
next
> > level of your web service adventure game!
> > But you never posted the structure of 'xmldata' and you never
posted
> > your 'Incoming' procedure. So there is nothing we could do for
you,
> > now.
> > Please compile your program with DBGVIEW(*LIST). Then start the
> > debugger and add a breakpoint at the top of your 'Incoming'
procedure.
> > Call the program and monitor the input parameters 'name', 'path'
and
> > 'depth'. Depending on their values you have to decide where to
store
> > the content of 'value', e.g.:
> > select;
> > when name = 'addr_1';
> > xmldata.addr_1 = value;
> > when name = 'addr_2';
> > xmldata.addr_2 = value;
> > ...
> > other;
> > ...
> > endsl;
> > Thomas.
> > ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx schrieb am 24.02.2011
13:02:30:
> > > Von: mr.singhjitender@xxxxxxxxx
> > > An: ftpapi@xxxxxxxxxxxxxxxxxxxxxx
> > > Datum: 24.02.2011 13:11
> > > Betreff: Re: XML parse failed at line 1, col 0: no element
found
> > > Gesendet von: ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> > >
> > > Hi Scott,
> > >
> > >
> > > First of all Thanks a lot for you support.
> > >
> > >
> > >
> > > Now I am able to get the result as expected but on
httpapi_debug.txt
> > file on
> > > ifs.
> > >
> > > Please find attached the debug file.
> > >
> > >
> > >
> > > I am using the following code for address cleansing
> > >
> > >
> > >
> > > http_xproc( HTTP_POINT_ADDL_HEADER
> > >
> > > : %paddr(Add_SOAPACTION) );
> > >
> > >
> > >
> > > rc = http_url_post_xml(%trim(httplink)
> > >
> > > : %addr(SOAP) + 2
> > >
> > > : %len(SOAP)
> > >
> > > : *NULL
> > >
> > > : %paddr(Incoming)
> > >
> > > : %addr(xmldata)
> > >
> > > : HTTP_TIMEOUT
> > >
> > > : HTTP_USERAGENT
> > >
> > > : 'text/xml; charset=utf-8');
> > >
> > >
> > >
> > >
> > >
> > > The xmldata is blank I am not getting the result on xmdata
variable.
> > >
> > >
> > >
> > > Please suggest what I need to do now.
> > >
> > >
> > >
> > > Thanks & Regards
> > >
> > > Jitender Singh.
> > >
> > >
> > >
> > >
> > > On Wed, Feb 23, 2011 at 10:55 PM, Scott Klement
> > <sk@xxxxxxxxxxxxxxxx> wrote:
> > >
> > > > Hello Jitender,
> > > >
> > > > On 2/23/2011 7:11 AM, jitender singh wrote:
> > > > > When i have changed the URL got an 500 HTTP/1.1 500
Internal
> > Server
> > > > > Error .
> > > > >
> > > > > Please find attached the debug file.
> > > > > Please suggest how i can rid off from this error.
> > > >
> > > >
> > > >
> > > > 500 just means "an error occurred". To find out what the
error
> > was, you
> > > > have to look at the document that the web server is sending
you.
> > Note
> > > > that the 500 error does *not* mean that you didn't get a
response
> > from
> > > > the web server -- you did! You got a SOAP message in
response.
> > > >
> > > > I'll copy/paste it from your debug file, and add some line
breaks
> > to
> > > > make it easier to read. Here's the result:
> > > >
> > > > <soapenv:Envelope
> > > >
xmlns:soapenv="[1][1]http://schemas.xmlsoap.org/soap/envelope/"
> > > > xmlns:xsd="[2][2]http://www.w3.org/2001/XMLSchema"
> > > >
xmlns:xsi="[3][3]http://www.w3.org/2001/XMLSchema-instance">
> > > > <soapenv:Body>
> > > > <soapenv:Fault>
> > > > <faultcode>soapenv:Sender</faultcode>
> > > > <faultstring>
> > > > Could not retrieve the body of the SOAP request.
Error: An
> > > > invalid XML character (Unicode: 0x0) was found in
the
> > element
> > > > content of the document.
> > > > </faultstring>
> > > > <faultactor></faultactor>
> > > > <detail/>
> > > > </soapenv:Fault>
> > > > </soapenv:Body>
> > > > </soapenv:Envelope>
> > > >
> > > > So, clearly it is receiving the document you are sending,
but you
> > have a
> > > > bug somewhere in your code that's inserting an invalid
character.
> > > >
> > > > I also noticed that SoapUI capitalizes the <Record> element,
but
> > you
> > > > have it in lowercase like <record>. Please change that to a
> > capital R
> > > > (XML is case sensitive.)
> > > >
> > > > Good luck
> > > >
> >
----------------------------------------------------------------------
> > -
> > > > This is the FTPAPI mailing list. To unsubscribe, please go
to:
> > > > [4][4]http://www.scottklement.com/mailman/listinfo/ftpapi
> > > >
> >
----------------------------------------------------------------------
> > -
> > > >
> > > [Anhang "httpapi_debug.txt" gelöscht von Thomas
Raddatz/OBI/DE]
> > >
> >
----------------------------------------------------------------------
> > -
> > > This is the FTPAPI mailing list. To unsubscribe, please go
to:
> > > [5][5]http://www.scottklement.com/mailman/listinfo/ftpapi
> > >
> >
----------------------------------------------------------------------
> > -
> >
> > --
> > IMPORTANT NOTICE:
> > This email is confidential, may be legally privileged, and is
for the
> > intended recipient only. Access, disclosure, copying,
distribution, or
> > reliance on any of it by anyone else is prohibited and may be a
> > criminal
> > offence. Please delete if obtained in error and email
confirmation to
> > the sender.
> >
> > References
> >
> > 1. [6]http://schemas.xmlsoap.org/soap/envelope/
> > 2. [7]http://www.w3.org/2001/XMLSchema
> > 3. [8]http://www.w3.org/2001/XMLSchema-instance
> > 4. [9]http://www.scottklement.com/mailman/listinfo/ftpapi
> > 5. [10]http://www.scottklement.com/mailman/listinfo/ftpapi
> >
> >
----------------------------------------------------------------------
-
> > This is the FTPAPI mailing list. To unsubscribe, please go to:
> > [11]http://www.scottklement.com/mailman/listinfo/ftpapi
> >
----------------------------------------------------------------------
-
> >
> >
>
----------------------------------------------------------------------
-
> This is the FTPAPI mailing list. To unsubscribe, please go to:
> [12]http://www.scottklement.com/mailman/listinfo/ftpapi
>
----------------------------------------------------------------------
-
--
IMPORTANT NOTICE:
This email is confidential, may be legally privileged, and is for the
intended recipient only. Access, disclosure, copying, distribution, or
reliance on any of it by anyone else is prohibited and may be a
criminal
offence. Please delete if obtained in error and email confirmation to
the sender.
References
1. http://schemas.xmlsoap.org/soap/envelope/
2. http://www.w3.org/2001/XMLSchema
3. http://www.w3.org/2001/XMLSchema-instance
4. http://www.scottklement.com/mailman/listinfo/ftpapi
5. http://www.scottklement.com/mailman/listinfo/ftpapi
6. http://schemas.xmlsoap.org/soap/envelope/
7. http://www.w3.org/2001/XMLSchema
8. http://www.w3.org/2001/XMLSchema-instance
9. http://www.scottklement.com/mailman/listinfo/ftpapi
10. http://www.scottklement.com/mailman/listinfo/ftpapi
11. http://www.scottklement.com/mailman/listinfo/ftpapi
12. http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------
This is the FTPAPI mailing list. To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------
- References:
- XML parse failed at line 1, col 0: no element found
- Re: XML parse failed at line 1, col 0: no element found
- Re: XML parse failed at line 1, col 0: no element found
- Re: XML parse failed at line 1, col 0: no element found
- Re: XML parse failed at line 1, col 0: no element found
- Re: XML parse failed at line 1, col 0: no element found
- Re: XML parse failed at line 1, col 0: no element found
- Re: XML parse failed at line 1, col 0: no element found
- Re: XML parse failed at line 1, col 0: no element found
- Re: XML parse failed at line 1, col 0: no element found
- Antwort: Re: XML parse failed at line 1, col 0: no element found