[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Versioning of LIBHTTP
William,
This is your code as you supplied it:
// Parse return data for ZMaterialGetDetail
Select;
When Name = 'ShortText';
Eval GetDetail.O_ShortText = Value;
When Name = 'Indgrosdet';
Eval GetDetail.O_GrosDetail = Value;
EndSl;
In the SOAP response there are no elements with these name present
('ShortText' 'Indgrosdet'), so it is only logical that you do not get values
for these fields.
If these elements are mandatory, and you are sure your service request
provides valid data, then I think you should go back to the SOAP service
provider, and see if they made any changes, for it seems the response you
get is not valid.
That does make sense, since you never said you changed the HTTPAPI or the
program that uses it.
----- Original Message -----
From: "Ha, William" <William.Ha@xxxxxxxx>
To: "'HTTPAPI and FTPAPI Projects'" <ftpapi@xxxxxxxxxxxxxxxxxxxxxx>
Sent: Tuesday, July 12, 2011 6:46 PM
Subject: RE: Versioning of LIBHTTP
Well i truncate the rest of the line when I do the Copy/Paste. The whole
line is like that:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";
xmlns:urn="urn:sap-com:document:sap:soap:functions:mc-sttyle">
<soapenv:Header> </soapenv:Header> <soapenv:Body>
<urn:zMaterialGetDetail> <ILanguage>F</ILanguage>
<IMaterial>000000000013455401</IMaterial> <TAttributs>
<item> <Zattribut/> <Descattrribut/>
</item> </TAttributs> <TBannerListingSel> <item>
<Salesorg/> <Distrchannel/> </item>
</TBannerListingSel> <TBannerPrice> <item>
<Salesorg/>> <Distrchannel/> <Pds>0</Pds>
</item> </TBannerPrice> <TIngredients> <item>
<Tdformat/> <Tdline/> </item>
</TIngredients> <TThemes> <item> <Ztheme/>
<Desctheme/> </item> </TThemes> <TUpc>
<item> <Salesorg></Salesorg>
<Distrchannel></Distrchannel> <Indgrosdet></Indgrosdet>
<Unit></Unit> <Upc></Upc> <Upctype></Upctype>
<Upcprincipal></Upcprincipal> <Empaquetage></Empaquetage>
</item> </TUpc> <TUpcSel> <item>
<Salesorg>CL02</Salesorg> <Distrchannel>09</Distrchannel>
</item> </TUpcSel> </urn:zMaterialGetDetail>
</soappenv:Body></soapenv:Envelope>
-----Message d'origine-----
De : ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
[mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx] De la part de Mike Krebs
Envoyé : mardi 12 juillet 2011 12:38
À : HTTPAPI and FTPAPI Projects
Objet : RE: Versioning of LIBHTTP
Well according to this, the program is supposed to send "Content-Length:
1601" bytes but sent only:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";
And the server responded with:
HTTP/1.1 200 OK
Then the server was supposed to send "content-length: 463" bytes of type
"accept: text/xml" but appears to have only sent:
<soap-env:Envelope xmlns:soap-env="http://schemas.xmlsoap.org/
So, no wonder you have parsing problems!
-----Original Message-----
From: ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
[mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of Ha, William
Sent: Tuesday, July 12, 2011 10:20 AM
To: 'HTTPAPI and FTPAPI Projects'
Subject: RE: Versioning of LIBHTTP
Sorry for the delay. Here's my Debug Log. Hope it's useful.
http_persist_post(): entered
http_long_ParseURL(): entered
do_post(): entered
POST /sap/bc/srt/rfc/sap/ZWS_MATERIAL_INFO?sap-client=256 HTTP/1.1
Host: sapdve.corp.metro.ca:80
User-Agent: http-api/1.23
Content-Type: text/xml
Expect: 100-continue
Content-Length: 1601
Authorization: Basic V0VCX1NFUlZJQ0VTOnBlbnRpdW
Cookie: $Version=0; sap-usercontext=sap-client=256; $Path=/; $Version=0; my
recvresp(): entered
HTTP/1.1 100 Continue
Server: SAP NetWeaver Application Server (ICM)
SetError() #13: HTTP/1.1 100 Continue
senddoc(): entered
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";
recvresp(): entered
HTTP/1.1 200 OK
set-cookie: MYSAPSSO2=AjExMDABAAxXRUJfU0VSVklDRVMCAAMxNDUDAAhEVkUgICAgIAQAD
content-type: text/xml; charset=utf-8
content-length: 463
accept: text/xml
sap-srt_id: 20110712/111023/v1.00_final_6.40/4E1C6C11347218DBE
server: SAP Web Application Server (1.0;700)
SetError() #13: HTTP/1.1 200 OK
recvdoc parms: identity 463
header_load_cookies() entered
cookie_parse() entered
cookie = MYSAPSSO2=AjExMDABAAxXRUJfU0VSVklDRVMCAAMxNDUDAAhEVk
cookie attr mysapsso2=AjExMDABAAxXRUJfU0VSVklDRVMCAAMxNDUDAAhE
cookie attr path=/
cookie attr domain=.corp.metro.ca
recvdoc(): entered
SetError() #0:
<soap-env:Envelope xmlns:soap-env="http://schemas.xmlsoap.org/
http_close(): entered
-----Message d'origine-----
De : ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
[mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx] De la part de Mike Krebs
Envoyé : mardi 12 juillet 2011 10:29
À : HTTPAPI and FTPAPI Projects
Objet : RE: Versioning of LIBHTTP
Not useful, William!
Are you saying that there is a problem with HTTPAPI? With Expat? With your
code? Are you looking for help? Or just wanted to let off some steam?
If you would like help, no matter where you think the problem is, give us
something we can look at. First, turn on debug and attach the whole file
(cleansing any proprietary data like passwords). Second, provide us some
code so we can see if your code matches the situation in the debug file.
If on the other hand, you just wanted to let off some steam, ppsssssstttttt!
-----Original Message-----
From: ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
[mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of Ha, William
Sent: Tuesday, July 12, 2011 8:07 AM
To: 'HTTPAPI and FTPAPI Projects'
Subject: RE: Versioning of LIBHTTP
Hi Scott,
I am glad to have you. Well my program is running fine for about a month and
suddenly without any change on my source code or server, it start to
malfunctioning. I used to get values for my 'ShorText' and 'Indgrosdet'
variables. But now when I debug my function mapMaterialGetDetail, I noticed
that the scans brings back 5 odd variables names with blanks as values as
shown below:
n0:MessageID
n1:Action
soap-env:Header
soap-env:Body
soap-env:Envelope
Since the function is running without any problem I did get a ReturnCode =
1. So I ended with no errors and nothing for my variables 'ShorText' and
'Indgrosdet'
-----Message d'origine-----
De : ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
[mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx] De la part de Scott Klement
Envoyé : lundi 11 juillet 2011 17:04
À : ftpapi@xxxxxxxxxxxxxxxxxxxxxx
Objet : Re: Versioning of LIBHTTP
Hi William,
Unfortunately, I really don't understand enough of your question to help
you.
You seem to be telling me that HTTPAPI shouldn't be returning 1, it
should be returning something else. Okay, let's go with that...
What should it be returning? And under which circumstance?
Can you post an HTTPAPI debug log (httpapi_debug.txt) that shows the
situation in which it's malfunctioning? Preferably with a description
of what HTTPAPI should do differently?
On 7/11/2011 2:56 PM, Ha, William wrote:
>
> My returnCode is a 1. So there is no error for the call. I can see
> the odd returning variables names thru a Debug session. I get my
> variables in a standard procedure as below:
>
> ReturnCode =
> http_post_xml( Http_Addrs
> : %Addr(Soap) + 2
> : %Len(Soap)
> : *NULL
> : %Paddr(mapMaterialGetDetail)
> : %Addr(MaterialGetDetail)
> : HTTP_TIMEOUT
> : HTTP_USERAGENT
> );
>
> // Verify for errors
> Select;
> // Time out
> WHen (ReturnCode = 0);
> Eval ErrMsg = %Trim(Message(07));
> // Error exist
> WHen (ReturnCode<> 1);
> Error = Http_error();
> // Show a formatted message to the user in case of 500 message
> If %Scan('HTTP/1.1 500' :Error) = 0;
> Eval ErrMsg = %Trim(Message(06)) + ' ... ' + %Trim(Error);
> EndIf;
> EndSl;
>
> P mapMaterialGetDetail...
> P B
> D PI
> D GetDetail LikeDs(MaterialGetDetail)
> D Depth 10I 0 Value
> D Name 1024A Varying Const
> D Path 24576A Varying Const
> D Value 32767A Varying Const
> D Attrs * Dim(32767) Const Options(*Varsize)
>
> * Local variables
> D* None
>
> /free
>
> // Parse return data for ZMaterialGetDetail
> Select;
> When Name = 'ShortText';
> Eval GetDetail.O_ShortText = Value;
> When Name = 'Indgrosdet';
> Eval GetDetail.O_GrosDetail = Value;
> EndSl;
> /End-free
>
> P mapMaterialGetDetail...
> P E
>
>
> -----Message d'origine-----
> De : ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> [mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx] De la part de Mike Krebs
> Envoyé : lundi 11 juillet 2011 15:46
> À : HTTPAPI and FTPAPI Projects
> Objet : RE: Versioning of LIBHTTP
>
> Scott had done a pretty good job of retaining compatibility. If you want
> to jump to latest (even latest Beta-very stable), you should be fine.
>
> Are you sure you didn't get an error from the server? Maybe you didn't get
> a communication error but it looks oddly like you pulled some error
> information in the return fields. Where did you find "some variables"? Are
> you ignoring the return codes in your programs? Are you keeping a log of
> the sent/received data?
>
> *************************************************
> Hi all,
>
> I want to know if each version of LIBHTTP is backward compatible. I am
> using right now the version 1.23. It is working fine up to a few days ago.
> And suddenly without any modifications on my source codes, one of my call
> to the procedure http_post_xml did not return all the parms that I am
> supposed to get. Instead of that I got without any error, some variables
> like below:
>
> n0:MessageID
> n1:Action
> soap-env:Header
> soap-env:Body
> soap-env:Envelope
>
> -----------------------------------------------------------------------
> This is the FTPAPI mailing list. To unsubscribe, please go to:
> 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
> -----------------------------------------------------------------------
>
-----------------------------------------------------------------------
This is the FTPAPI mailing list. To unsubscribe, please go to:
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
-----------------------------------------------------------------------
-----------------------------------------------------------------------
This is the FTPAPI mailing list. To unsubscribe, please go to:
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
-----------------------------------------------------------------------
-----------------------------------------------------------------------
This is the FTPAPI mailing list. To unsubscribe, please go to:
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
-----------------------------------------------------------------------
-----------------------------------------------------------------------
This is the FTPAPI mailing list. To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------