Add security handlers to faultsHandlers on client and server side, should fix the problem.
On 12/19/06, Edelmann Alexander (CI/ACA3) <[EMAIL PROTECTED]> wrote:
Hello, I am using the dynamic client and expect to get an encrypted response from the remote web service. As soon as the client gets a SOAP - fault from the server, the client WSS4JInHandler is invoked throwing an exception that the incoming message does not contain a security header. As far as I know that security ought not be applied to outgoing soap faults. Therefore the client should not try to look for security information within the soap envelope but for some reason it does that anyways. As I looked through the handlers in the parsing phase I discovered that the ReadHeadersHandler ,being in charge of looking for soap-faults among other things, gets invoked after the WSS4JInHandler. Isn't that handler supposed to be configured before the WSS4JInHandler in order to check for possible faults returned from the server? I am looking forward to your advises. Best regards, Alexander Edelmann Robert Bosch GmbH
-- ----- When one of our products stops working, we'll blame another vendor within 24 hours. --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
