Re: Axis2 and dotNet interoperateability
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 addressing-1.0.mar to the directory where axis2.jar is. Only putting addressing-1.0.mar in CLASSPATH environment variable won't work. So I engaged addressing sucessfully at the client side. The soap message is, xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsa=" http://www.w3.org/2005/08/addressing"> http://127.0.0.1:8080/axis2/services/MyService http://192.168.2.110:6060/axis2/services/__ANONYMOUS_SERVICE__/__OPERATION_OUT_IN__ urn:uuid:79588982FE3D3323FD11594838301071 urn:echo http://example1.org/example1"> Axis2 Echo String All addressing headers are there. It looks good to me. At Axis2 server side, I have in axis2.xml and copied phaseorder tags from your email to the axis2.xml. But I still don't see addressing is being engaged. The soap message is, xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"> http://example1.org/example1" xmlns:tns="http://ws.apache.org/axis2"> Axis2 Echo String is still empty. I don't know what I need to configure axis2 to engage addressing at server side. Thanks for your help!vikeOn 9/28/06, R B <[EMAIL PROTECTED]> wrote: 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. ( http://www.developer.com/services/article.php/3620661).About setting the adressing module at the launch of Axis2, I think it is enabled by default. If it's not, you have to modify your axis2.xml file and have something like this (this is configured to enable SOAPMonitor as well): class="org.apache.axis2.engine.RequestURIBasedDispatcher "> class="org.apache.axis2.engine.SOAPActionBasedDispatcher "> class="org.apache.axis2.engine.AddressingBasedDispatcher "> class="org.apache.axis2.engine.SOAPMessageBodyBasedDispatcher "> class="org.apache.axis2.engine.InstanceDispatcher "> class="org.apache.axis2.engine.RequestURIBasedDispatcher "> class="org.apache.axis2.engine.SOAPActionBasedDispatcher "> class="org.apache.axis2.engine.RequestURIBasedDispatcher"> class="org.apache.axis2.engine.SOAPActionBasedDispatcher"> class="org.apache.axis2.engine.AddressingBasedDispatcher"> class="org.apache.axis2.engine.SOAPMessageBodyBasedDispatcher"> class="org.apache.axis2.engine.InstanceDispatcher"> Hope that can help,RBOn 9/26/06, scott ken <[EMAIL PROTECTED]> wrote: David,I started the discussion using my yahoo email account. I suspect that Yahoo treats the Axis2 mailinglist as 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 webpage. But it seems not change the result. The request/reply soap messages are still the same. Do you know what else steps I need to performa to make addressing effect. And another question is, if I don't want to engage addressing dynamically from Axis2 admin servlet but want to do it in configuration files, is it possible?Thanks,vickDavid Illsley < [EMAIL PROTECTED]> wrote: Looks to me like you need to engage the addressing module in the axis2server so that there are addressing headers in the response. See theAxis2 documentaton for how to do this. DavidOn 21/09/06, scott ken wrote:> My C# client (.dotNet 2.0 and WSE 3.0) generated the following SOAP> message.
Re: Axis2 and dotNet interoperateability
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. ( http://www.developer.com/services/article.php/3620661).About setting the adressing module at the launch of Axis2, I think it is enabled by default. If it's not, you have to modify your axis2.xml file and have something like this (this is configured to enable SOAPMonitor as well): class="org.apache.axis2.engine.RequestURIBasedDispatcher "> class="org.apache.axis2.engine.SOAPActionBasedDispatcher "> class="org.apache.axis2.engine.AddressingBasedDispatcher "> class="org.apache.axis2.engine.SOAPMessageBodyBasedDispatcher "> class="org.apache.axis2.engine.InstanceDispatcher "> class="org.apache.axis2.engine.RequestURIBasedDispatcher "> class="org.apache.axis2.engine.SOAPActionBasedDispatcher "> class="org.apache.axis2.engine.RequestURIBasedDispatcher"> class="org.apache.axis2.engine.SOAPActionBasedDispatcher"> class="org.apache.axis2.engine.AddressingBasedDispatcher"> class="org.apache.axis2.engine.SOAPMessageBodyBasedDispatcher"> class="org.apache.axis2.engine.InstanceDispatcher"> Hope that can help,RBOn 9/26/06, scott ken <[EMAIL PROTECTED]> wrote: David,I started the discussion using my yahoo email account. I suspect that Yahoo treats the Axis2 mailinglist as 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 webpage. But it seems not change the result. The request/reply soap messages are still the same. Do you know what else steps I need to performa to make addressing effect. And another question is, if I don't want to engage addressing dynamically from Axis2 admin servlet but want to do it in configuration files, is it possible?Thanks,vickDavid Illsley < [EMAIL PROTECTED]> wrote: Looks to me like you need to engage the addressing module in the axis2server so that there are addressing headers in the response. See theAxis2 documentaton for how to do this. DavidOn 21/09/06, scott ken wrote:> My C# client (.dotNet 2.0 and WSE 3.0) generated the following SOAP> message.>> > >> 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"> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance "> xmlns:xsd=" http://www.w3.org/2001/XMLSchema"> xmlns:xop="http://www.w3.org/2004/08/xop/include "> xmlns:soap=" http://schemas.xmlsoap.org/soap/envelope/">> xmlns:wsu=" http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">> > > > urn:uuid:8a8309c1-a21d-48ff-aa52-2647bb377cfc> > > >> http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous> > > > http://localhost:8080/axis2/services/CMBWebService> > > > wsu:Id="Timestamp-010f1103-934c-44fb-8778-1251c874e66e"> > 2006-09-20T23:12:21Z> 2006-09-20T23:17:21Z> > > > > > > > > >> The reply message from Axis2 server is>> > > xmlns:soapenv=" http://schemas.xmlsoap.org/soap/envelope/">> > > > > > > >> The C# client encountered this exception>> Unhandled Exception:> Microsoft.Web.Services3.Addressing.AddressingFault: Message> Information Header Required ---> Micros > oft.Web.Services3.Addressing.AddressingFormatException:> WSE202: The> Action header is required when other address headers> are present.>--- End of inner exception stack trace --- >at> Microsoft.Web.Services3.Addressing.AddressingHeaders.CheckValid()>at> Microsoft.Web.Services3.Addressing.AddressingHeaders.Load(SoapEnvelope> envelope)>at Microsoft.Web.Services3.SoapEnvelope.PostLo
Re: Axis2 and dotNet interoperateability
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 webpage. But it seems not change the result. The request/reply soap messages are still the same. Do you know what else steps I need to performa to make addressing effect. And another question is, if I don't want to engage addressing dynamically from Axis2 admin servlet but want to do it in configuration files, is it possible?Thanks,vickDavid Illsley < [EMAIL PROTECTED]> wrote: Looks to me like you need to engage the addressing module in the axis2server so that there are addressing headers in the response. See theAxis2 documentaton for how to do this.DavidOn 21/09/06, scott ken wrote:> My C# client (.dotNet 2.0 and WSE 3.0) generated the following SOAP> message.>> > >> 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 "> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> xmlns:xsd=" http://www.w3.org/2001/XMLSchema"> xmlns:xop="http://www.w3.org/2004/08/xop/include"> xmlns:soap=" http://schemas.xmlsoap.org/soap/envelope/">> xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd ">> > > > urn:uuid:8a8309c1-a21d-48ff-aa52-2647bb377cfc> > > >> http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous> > > > http://localhost:8080/axis2/services/CMBWebService > > > > wsu:Id="Timestamp-010f1103-934c-44fb-8778-1251c874e66e">> 2006-09-20T23:12:21Z> 2006-09-20T23:17:21Z> > > > > > > > > >> The reply message from Axis2 server is>> > > xmlns:soapenv=" http://schemas.xmlsoap.org/soap/envelope/">> > > > > > > >> The C# client encountered this exception>> Unhandled Exception: > Microsoft.Web.Services3.Addressing.AddressingFault: Message> Information Header Required ---> Micros> oft.Web.Services3.Addressing.AddressingFormatException:> WSE202: The> Action header is required when other address headers > are present.>--- End of inner exception stack trace --->at> Microsoft.Web.Services3.Addressing.AddressingHeaders.CheckValid()>at> Microsoft.Web.Services3.Addressing.AddressingHeaders.Load (SoapEnvelope> envelope)>at Microsoft.Web.Services3.SoapEnvelope.PostLoad(Boolean> loadAddressing)>at Microsoft.Web.Services3.SoapEnvelope.PostLoad()>at Microsoft.Web.Services3.SoapEnvelope.Load (XmlReader> reader)>at> Microsoft.Web.Services3.Mime.XopDocument.LoadStartPart(MimePart> startPart)>at> Microsoft.Web.Services3.Mime.XopDocument.LoadFromXopPackage(String > contentType, Stream stream)>at> Microsoft.Web.Services3.Xml.SoapEnvelopeReaderWrapper..ctor(SoapClientMessage> message, String messageContentType)>at> Microsoft.Web.Services3.WebServicesClientProtocol.GetReaderForMessage (SoapClientMessage> message, Int32 bufferSize)> at> System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage> message, WebResponse response,> Stream responseStream, Boolean asyncCall) >at> System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String> methodName, Object[] parameters)>> I guess it's about some configuration on client side or server side. > Can someone tell me what the fix is?>> Thanks in advance,>> vick>>> > Stay in the know. Pulse on the new Yahoo.com. Check it out.>>-- David Illsley - IBM Web Services Development-To unsubscribe, e-mail: [EMAIL PROTECTED]For additional commands, e-mail: [EMAIL PROTECTED] -Get your email and more, right on the new Yahoo.com --0-1468242578-1159300441=:31885Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: 8bitHi, David,I engaged the addressing module from axis2 admin webpage. But it seems not change the result. The request/reply soap messages are still the same. Do you know what else steps I need to performa to make addressing effect. And another question is, if I don't want to engage addressing dynamically from Axis2 admin servlet but want to do it in configuration files, is it possible?Thanks,vickDavid Illsley < [EMAIL PROTECTED]> wrote: Looks to me like you need to engage the addressing module in the axis2server so that there are addressing headers in the response. See theAxis2 documentaton for how to do this.DavidOn 21/09/06, scott ken < [EMAIL PROTECTED]> wrote:> My C# client (.dotNet 2.0 and WSE 3.0) generated the following SOAP> message.>> > >> 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
Re: Axis2 and dotNet interoperateability
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 SOAP message. 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"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:xop="http://www.w3.org/2004/08/xop/include"; xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"; xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd";> urn:uuid:8a8309c1-a21d-48ff-aa52-2647bb377cfc http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous http://localhost:8080/axis2/services/CMBWebService 2006-09-20T23:12:21Z 2006-09-20T23:17:21Z The reply message from Axis2 server is http://schemas.xmlsoap.org/soap/envelope/";> The C# client encountered this exception Unhandled Exception: Microsoft.Web.Services3.Addressing.AddressingFault: Message Information Header Required ---> Micros oft.Web.Services3.Addressing.AddressingFormatException: WSE202: The Action header is required when other address headers are present. --- End of inner exception stack trace --- at Microsoft.Web.Services3.Addressing.AddressingHeaders.CheckValid() at Microsoft.Web.Services3.Addressing.AddressingHeaders.Load(SoapEnvelope envelope) at Microsoft.Web.Services3.SoapEnvelope.PostLoad(Boolean loadAddressing) at Microsoft.Web.Services3.SoapEnvelope.PostLoad() at Microsoft.Web.Services3.SoapEnvelope.Load(XmlReader reader) at Microsoft.Web.Services3.Mime.XopDocument.LoadStartPart(MimePart startPart) at Microsoft.Web.Services3.Mime.XopDocument.LoadFromXopPackage(String contentType, Stream stream) at Microsoft.Web.Services3.Xml.SoapEnvelopeReaderWrapper..ctor(SoapClientMessage message, String messageContentType) at Microsoft.Web.Services3.WebServicesClientProtocol.GetReaderForMessage(SoapClientMessage message, Int32 bufferSize) at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall) at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters) I guess it's about some configuration on client side or server side. Can someone tell me what the fix is? Thanks in advance, vick Stay in the know. Pulse on the new Yahoo.com. Check it out. -- David Illsley - IBM Web Services Development - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
