I'm no .Net expert, but I think WS-Addressing is only supported in WSE 3.0. http://msdn2.microsoft.com/en-us/library/aa529362.aspx Which is a kind of add-on support library that you need to download for free from the Microsoft website. I don't know what is included in .NET 2.0. (Probably not WS-Addressing support, according to the info you supplied).
Now, in theory, if you can't get WSE 3.0 to work in your .NET 2.0 environment, you could attempt to write your own message handlers to handle WS-Addressing headers. But that would be a complex task, I think. But, in general, this page should help, for soap header manipulation in .NET (at least the basics, anyway). http://msdn2.microsoft.com/en-us/library/whew6x7f.aspx -jeff -----Original Message----- From: Jochen Zink [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 04, 2007 5:38 AM To: axis-user@ws.apache.org Subject: [Axis2] Problems with Statefull WebService and .NET client Hello, I have a StateFull WebService written with Axis2 1.1.1 with scope="soapsession". Know I want to develop a .NET client to test interoperability. It works well, I can call every Service Method. But the client ignores WS-Addressing information's. The ServiceGroupID is not sended back to the WebService. I know this is not a axis2 question, but I hope anybody here has written a .net 2.0 client, to consume a statefull webservice. With the wsdl.exe tool, I have generate a Proxy class. I can't access to the soap header (or I don't know how), to read the servicegroupID by hand and send it back. Does anyone know how does this work or where I can find information's about that? I try to search MSDN and google. Without useful results. Thanks a lot! _____________________________________________________________________ Der WEB.DE SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! http://smartsurfer.web.de/?mc=100071&distributionid=000000000066 --------------------------------------------------------------------- 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]
