cnblogs里有篇帖子
http://idior.cnblogs.com/articles/436801.html（
Applied WSE 3.0 to Web Service Project ），對于學習WS-Addressing是篇不錯的帖子。按照此貼的方法進行，在追蹤Soap消息時，拋出異常。在未開啟Client端WSE功能時，Soap Toolkit 3.0能追蹤到soap消息，而且，response顯示了wse的特性。
為了使用Soap Toolkit 3.0，我們在WS client端輸入的目標地址為：
http://localhost:8080/WSEWebService/Service.asmx。
Soap Toolkit 3.0設置為：
Listen
Local port:8080
Forward to
Destination:localhost
Destination:80
之所以這樣設置，因為在IIS里設置的本機Web Services為：
http://localhost:80/WSEWebService/Service.asmx。Soap Toolkit 在8080端口監聽來自client端的消息，并將消息遞交到IIS監聽的80端口。
可當開啟client端wse功能時，拋出如下異常：
查看 Soap Toolkit 監聽到的SOAP消息可以發現，Request消息的SoapHeader中, 目標地址仍然為
<wsa:To>http://localhost:8080/WSEWebService/Service.asmx</wsa:To> ，而不是
<wsa:To>http://localhost:80/WSEWebService/Service.asmx</wsa:To>.因此，destination不可達，拋出如上異常。
在網上查了資料發現：
“
WS-Addressing moves the destination URL of the message into the message to enable routing and scenarios where messages are delivered over multiple protocols. Before WS-Addressing the URL of the destination was only available in the protocol part of the message. Is you were sending a SOAP message over HTTP, the URL was stored in the HTTP part of the message. You had no access to the URL from within your SOAP processor – unless your Web server vendor chose to give you access to the HTTP headers.
Now with WS-Addressing built into WSE, the Web service platform can actually determine if a message was indeed intended for the service that received it because WSE adds the <to> element to the header of the SOAP message:
<wsa:To xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/03/addressing">
http://MyServer/MyService/Service.asmx</wsa:To>
WSE is actually being smart about the header and rejects messages where the destination in the <wsa:To> header and the URL in the HTTP header do not match.
One unfortunate consequence of this behavior is that you cannot use transparent tracing tools like tcpTrace and MSSoapT for message debugging. These tools act like an intermediary receiver and they do cause the URLs in the <To> header and in the HTTP header to not match.
”，大概意思也就是MSSoapt(Soap Toolkit )不支持WSE中WS-Addressing<wsa:To>。所以在調試WSE提供的特性時，不能再用 tcpTrace或者MSSoapT這樣的工具來追蹤Soap消息。
不過，好的消息是，WSE從2.0開始就提供了可以追蹤到SOAP消息的診斷工具。
勾選Enable Message Trace，在調試過程中，將生成InputTrace.webinfo和OutputTrace.webinfo文件，里面記錄了我們想要的信息，到此，不需要借助其他Trace工具便可追蹤到Soap消息。