Getting Exception faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Client?

You need to do one of two things: 1) Look on the web server that your SOAP requests are going to. In those logs you'll probably find the Exception being thrown on that side that is turning into the AxisFault 2) Use something like WireShark to trace the HTTP traffic. Although this won't give you a lot of information beyond what you already have, it will prove that the AxisFault is basically a client-side representation of an Exception thrown on the server side The stack trace you get in this instance (i.e.

, from SoapFaultBuilder) is entirely misleading, as it's the stack trace of the code that is creating a client-side representation of the server error rather than the server-side stack trace showing the actual problem.

You need to do one of two things: 1) Look on the web server that your SOAP requests are going to. In those logs you'll probably find the Exception being thrown on that side that is turning into the AxisFault. 2) Use something like WireShark to trace the HTTP traffic.

Although this won't give you a lot of information beyond what you already have, it will prove that the AxisFault is basically a client-side representation of an Exception thrown on the server side. The stack trace you get in this instance (i.e. , from SoapFaultBuilder) is entirely misleading, as it's the stack trace of the code that is creating a client-side representation of the server error rather than the server-side stack trace showing the actual problem.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.