Hi, I don't know if it can help. What I understood is that you try to access your service by using a SOAP session. As specified it the following document, you have to engage the adressing module on both sides (client and server), and change the scope of your service before engaging it. (
Thanks R B.I think my problem is that I didn't engage addressing both at client and server. Now I'm trying fix the problem. I started with Axis2 sample EchoNonBlockingDualClient. I put addressing-1.0.mar in the client classpath. Read archived mails in Axis2 mailinglist, I actually need to copy
David,I started the discussion using my yahoo email account. I suspect that Yahoo treats the Axis2 mailinglistas a spam. My second email to the mailinglist was bounced back. Now I'm using myGmail account to continue asking questions. Thanks!
I engaged the addressing module from axis2 admin
Looks to me like you need to engage the addressing module in the axis2
server so that there are addressing headers in the response. See the
Axis2 documentaton for how to do this.
David
On 21/09/06, scott ken [EMAIL PROTECTED] wrote:
My C# client (.dotNet 2.0 and WSE 3.0) generated the following
My C# client (.dotNet 2.0 and WSE 3.0) generated the following SOAP message. ?xml version='1.0' encoding='utf-8'? soap:Envelope xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing"
