I suspect the server you are talking to is returning an ordinary HTTP 400 Bad request, not a SOAP fault. The HTTP status code must be 500 for all SOAP faults. Services can sometimes respond with 400 Bad Request or 401 Unauthorized in addition to actual SOAP faults with code 500.
-----Original Message----- From: David Robertson [mailto:[EMAIL PROTECTED] Sent: Thursday, August 02, 2007 3:36 PM To: [email protected] Cc: Andrew Lake Subject: Transport error: 400 Error: Bad Request I'm wondering if something changed in the way a client handles SOAP faults between Axis2 1.1.1 and Axis2 1.2. Previously if a fault message was thrown, the client would receive the fault message. As of 1.2, we've always gotten the error in the subject line when a fault is thrown on the server. I believe that what comes back to the client is the correct message with the fault. This still occurs with the nightly build of 1.3. (We have modified our skeleton and exception classes to follow the latest code generation.) Any help would be greatly appreciated. -David Robertson --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
