Are Soap Webservices broken in Berlin?
Are Soap Webservices broken in Berlin?
Create a new soap werbserver ISAPI project and include the example functions
Compile it to a isapi.dll and deploy it.
If i want invoke per example the function "echodouble" i get a ESOAPHttpException "text/html instead of text/xml "
Compile the same project with seattle all works fine.
Create a new soap werbserver ISAPI project and include the example functions
Compile it to a isapi.dll and deploy it.
If i want invoke per example the function "echodouble" i get a ESOAPHttpException "text/html instead of text/xml "
Compile the same project with seattle all works fine.
I guess that exception comes from THTTPReqResp.CheckContentType? If so the problem is on the caller side that does not set the correct content type.
ReplyDeleteA standalone server (not ISAPI) works with request posted with Chrome extension "Postman". I probably wouldn't expect my test being standalone making a difference here, so I'm also wondering about the request your tested with. My (stripped down) Postman request:
ReplyDeletehttp://schemas.xmlsoap.org/soap/envelope/">
1.23456
Sorry for my late answer. I was too busy these days. I posted a new entry at Quality Central.
ReplyDeletehttps://quality.embarcadero.com/browse/RSP-16136
To Stefan:
The caller side is also a small delphi program. Compiling it with Seattle or Berlin makes no difference. In both cases it can call a isapi webservice compiled with seattle. Compiled with Berlin it does'nt work.
To Walter:
At moment i am very busy solving other issues here :-). As soon i can go back to the work where the issue occured i will make further tests.
Any way, thanks a lot for your investigations.
quality.embarcadero.com - Log in - Embarcadero Technologies