search

reficio / soap-ws

Java library, based on Spring-WS, that enables handling SOAP on a purely XML level
297 stars 145 forks source link

Status 500 in SoapClient.executePost (Fault) #19

Open skolorz opened 10 years ago

skolorz commented 10 years ago

In case of fault (return code 500) method throws a TransmissionException. Fault is not a transmission error, it's "Internal server error". Do you plan to modify this issue?

What about introducing new InternalServerEexception for code 500 with attribute entity. Client should be able to access the entity.

tombujok commented 10 years ago

Makes sense. Pull request with a patch and a test case appreciated. On Sep 25, 2013 8:46 AM, "Szymon" notifications@github.com wrote:

In case of fault (return code 500) method throws a TransmissionException. Fault is not a transmission error, it's "Internal server error". Do you plan to modify this issue?

What about introducing new InternalServerEexception for code 500 with attribute entity. Client should be able to access the entity.

— Reply to this email directly or view it on GitHubhttps://github.com/reficio/soap-ws/issues/19 .

MauroMombelli commented 9 years ago

the problem is that client.post(request);

Send a empty "SOAPAction" header , and server dislike it.

It the example i changed it to String response = client.post("http://www.webserviceX.NET/ConversionRate",request);

and not it works

ebett commented 8 years ago

Hi, is there a new version with the solution of this problem? Thank you.