Hi Martin, My header now looks like... <soapenv:Envelope xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope";> <soapenv:Header xmlns:wsa="http://www.w3.org/2005/08/addressing";> <wsa:To>...</wsa:To> <wsa:MessageID>...</wsa:MessageID> <wsa:Action>...</wsa:Action> <wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"; soapenv:mustUnderstand="true"> ...
Do you think my configuration is wrong? I am using the default conf file which I copied from the samples. For you reference I modified WSS4J for the issue: https://issues.apache.org/jira/browse/WSS-231 Thanks On 23 February 2011 13:26, Martin Gainty <[email protected]> wrote: > surprising as Microsoft had a member on the committee that drafted the > ws-addressing spec > <soapenv:Header xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing"; > specifically > http://schemas.xmlsoap.org/ws/2004/08/addressing/ > > of course you can change the wsa to point to another xsd > but you would break interoperability with expected WS-addressing compliant > structures > > from this perspective the fault is WCF does not adhere to the ws-addressing > spec > what does Microsoft say? > > Martin Gainty > ______________________________________________ > Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité > > Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene > Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte > Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht > dient lediglich dem Austausch von Informationen und entfaltet keine > rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von > E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. > > Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le > destinataire prévu, nous te demandons avec bonté que pour satisfaire > informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie > de ceci est interdite. Ce message sert à l'information seulement et n'aura > pas n'importe quel effet légalement obligatoire. Étant donné que les email > peuvent facilement être sujets à la manipulation, nous ne pouvons accepter > aucune responsabilité pour le contenu fourni. > > > > >> From: [email protected] >> Date: Wed, 23 Feb 2011 12:37:29 +0000 >> Subject: Re: .net and axis2/rampart >> To: [email protected] >> >> Hi, FYI regarding the previous issue, WCF did not like the location of >> the timestamp element and I have modified the wss4j library to output >> the timestamp before the signature element. >> >> However, I now have the issue with the order of the following elements >> output by Axis2: >> >> <wsa:To>...</wsa:To> >> <wsa:MessageID>...</wsa:MessageID> >> <wsa:Action>...</wsa:Action> >> >> WCF expects the order >> >> <wsa:Action>...</wsa:Action> >> <wsa:MessageID>...</wsa:MessageID> >> <wsa:To>...</wsa:To> >> >> Would anyone know if it's possible to adjust the order, or know which >> libraries I need to modify? >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
