Pease disregard my question. I found were the problem was. The problem was that for my working webservice the hook was defined and called during the process. This hook had access to the SOAP message and did some processing on it. As the message had been modified after securing it, the hook processed the modified SOAP differently and thrown the exeption ' Bad username/password in SOAP header 'null'/'null'' . So the exception had been thrown by my own implemented hook.
Sorry if somebody started to look into it, Thanks, Paulius -- View this message in context: http://www.nabble.com/Bad-username-password-in-SOAP-header-%27null%27-%27null%27-tf2157591.html#a5980306 Sent from the WSS4J forum at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
