I reviewed WSSecurityEngine code for WSS4j 1.1.0 and I am unhappy to see so many problems.
Recently, I have been trying to throw a WSSecurityException from the callback for USERNAME_TOKEN_UKNOWN usage and whatever I put in the message of the exception the WSSecurityEngine always catches it and puts it's own "No Password for..." message. Can you please rethink this logic?! best to all of you! Stanimir Stanev (Stanley) Senior Java Developer Momentum SI, Austin TX http://www.momentumsi.com http://www.stanev.com __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
