Mailing-List: contact axis-user-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-user@ws.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
Message-ID: <46B25C39.3070307@lbl.gov>
Date: Thu, 02 Aug 2007 15:35:37 -0700
From: David Robertson <dwrobertson@lbl.gov>
User-Agent: Thunderbird 2.0.0.5 (Windows/20070716)
MIME-Version: 1.0
To: axis-user@ws.apache.org
CC: Andrew Lake <alake@internet2.edu>
Subject: Transport error: 400 Error: Bad Request
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

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: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org