I think this may address your issue: http://svn.apache.org/viewvc?view=revision&revision=912481
In that change a namespace that was declare in a sibling-scoped element would be used undeclared in another sibling element. This patch keeps track of namespaces better. Let us know if this patch fixes your issue or not. I know that I'm interested. -Allan From: Avijit Ajay [mailto:avijit.a...@tcs.com] Sent: Thursday, April 22, 2010 4:41 AM To: java-user@axis.apache.org Subject: WSU prefix not being inserted in Security token reference Hello, I am trying to access a Weblogic web service from a Axis 2 client. The web service is secured using SAML tokens. While trying to access the web service, I get the following error : Error at Line:0 Prefix [wsu] used without binding it to a namespace URI When i checked the request I found that the <wsse:SecurityTokenReference wsu:Id="STRId-8122E465643B3A4E3B12719228567883"> <wsse:Reference URI="#CertId-8122E465643B3A4E3B12719228567181" ValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3";> </wsse:Reference> </wsse:SecurityTokenReference> The name space has not been declared in the Security token reference element, which probably causes the problem. I am using Rampart 1.5 for security. I would appreciate any guidance on this matter. Thanks in advance. Avijit Ajay =====-----=====-----===== Notice: The information contained in this e-mail message and/or attachments to it may contain confidential or privileged information. If you are not the intended recipient, any dissemination, use, review, distribution, printing or copying of the information contained in this e-mail message and/or attachments to it are strictly prohibited. If you have received this communication in error, please notify us by reply e-mail or telephone and immediately and permanently delete the message and any attachments. Thank you
