Re: faultstringThe endpoint reference (EPR) for the Operation not found is http://122.22.2.22:9090/outboundws/services/Outbound and the WSA Action = /faultstring
Also note that Axis2 does not support SOAP Encoding -- and your messages are SOAP encoded. Anne On 10/10/07, G71 [EMAIL PROTECTED] wrote: Ok... Thank you... The 'core' problem is: when i set xmlns: soapenv:Body m:outboundService xmlns:m=http://www.pippo.it/blabla/; or in the other service soapenv:Body m:SMSService xmlns:m=http://www.pippo.it/blabla/; i've the same 'OK' result... Why? Why receive i a result of failure only for outbound in the case of setting in xmlns:m=http://www.paperino.it/lalala/; for the services? I tryed to modify the wsdl... but i don't receive the right response. Is wsdl check from the engine...or what??? Who check the xmlns and how is it check?... thank you... Amila Suriarachchi wrote: how did you create these two services. here since you don't have the soapaction and the don't use the addressing the only way to find the operation is to using the body based dispatching. body based dispatching works only if all your operations has unique input element qnames. i.e if there are two operations with same input element then axis2 can not find the correct operation. Can you check for this? Amila. On 10/9/07, G71 [EMAIL PROTECTED] wrote: Hi, i've this problem with axis2: i've two services in the same wsdl but the response of one of this service is faultstringThe endpoint reference (EPR) for the Operation not found is http://172.31.4.49:9090/outboundws/services/Outbound and the WSA Action = /faultstring i've read the but i didn't found the solution: http://wso2.org/library/176 Why the response of one of this is correct and the second is not correct? The soap action is null in all this message I post the example: POST /outboundws/services/Outbound HTTP/1.0 Host: 172.31.4.49:9090 Content-Type: text/xml; charset=utf-8 Content-Length: 1432 SOAPAction: ?xml version='1.0' encoding='UTF-8'? soapenv:Envelope xmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/ xmlns:xsi=http://www.w3.org/1999/XMLSchema-instance; xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:encodingStyle=http://schemas.xmlsoap.org/soap/encoding/; xmlns:xsd=http://www.w3.org/1999/XMLSchema; soapenv:Body m:outboundService dataSetVersion=1.0 xmlns:m=http://www.fasfafdw.it/outboundService/outboundService; appuntamento bla bla bla/appuntamento /m:outboundService /soapenv:Body /soapenv:Envelope In this case the response is not correct: Instead in the call of this service is correct: POST /outboundws/services/Outbound HTTP/1.0 Host: 172.31.4.49:9090 Content-Type: text/xml; charset=utf-8 Content-Length: 654 SOAPAction: ?xml version='1.0' encoding='UTF-8'? soapenv:Envelope xmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/ xmlns:xsi=http://www.w3.org/1999/XMLSchema-instance; xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:encodingStyle=http://schemas.xmlsoap.org/soap/encoding/; xmlns:xsd=http://www.w3.org/1999/XMLSchema; soapenv:Body m:SMSService dataSetVersion=1.0 xmlns:m=xmlns:m=http://www.fasfafdw.it/outboundService/SMSService; message cell=+393358478769 textMessagetestomessagio./textMessage /message /m:SMSService /soapenv:Body /soapenv:Envelope -- View this message in context: http://www.nabble.com/faultstring%3EThe-endpoint-reference-%28EPR%29-for-the-Operation-not-found-is-http%3A--122.22.2.22%3A9090-outboundws-services-Outbound-and-the-WSA-Action-%3D-%3C-faultstring%3E-tf4592781.html#a13111387 Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Amila Suriarachchi, WSO2 Inc. -- View this message in context: http://www.nabble.com/faultstring%3EThe-endpoint-reference-%28EPR%29-for-the-Operation-not-found-is-http%3A--122.22.2.22%3A9090-outboundws-services-Outbound-and-the-WSA-Action-%3D-%3C-faultstring%3E-tf4592781.html#a13132036 Sent from the Axis - User mailing list archive at Nabble.com. - 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]
Re: faultstringThe endpoint reference (EPR) for the Operation not found is http://122.22.2.22:9090/outboundws/services/Outbound and the WSA Action = /faultstring
how did you create these two services. here since you don't have the soapaction and the don't use the addressing the only way to find the operation is to using the body based dispatching. body based dispatching works only if all your operations has unique input element qnames. i.e if there are two operations with same input element then axis2 can not find the correct operation. Can you check for this? Amila. On 10/9/07, G71 [EMAIL PROTECTED] wrote: Hi, i've this problem with axis2: i've two services in the same wsdl but the response of one of this service is faultstringThe endpoint reference (EPR) for the Operation not found is http://172.31.4.49:9090/outboundws/services/Outbound and the WSA Action = /faultstring i've read the but i didn't found the solution: http://wso2.org/library/176 Why the response of one of this is correct and the second is not correct? The soap action is null in all this message I post the example: POST /outboundws/services/Outbound HTTP/1.0 Host: 172.31.4.49:9090 Content-Type: text/xml; charset=utf-8 Content-Length: 1432 SOAPAction: ?xml version='1.0' encoding='UTF-8'? soapenv:Envelope xmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/ xmlns:xsi=http://www.w3.org/1999/XMLSchema-instance; xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:encodingStyle=http://schemas.xmlsoap.org/soap/encoding/; xmlns:xsd=http://www.w3.org/1999/XMLSchema; soapenv:Body m:outboundService dataSetVersion=1.0 xmlns:m=http://www.fasfafdw.it/outboundService/outboundService; appuntamento bla bla bla/appuntamento /m:outboundService /soapenv:Body /soapenv:Envelope In this case the response is not correct: Instead in the call of this service is correct: POST /outboundws/services/Outbound HTTP/1.0 Host: 172.31.4.49:9090 Content-Type: text/xml; charset=utf-8 Content-Length: 654 SOAPAction: ?xml version='1.0' encoding='UTF-8'? soapenv:Envelope xmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/ xmlns:xsi=http://www.w3.org/1999/XMLSchema-instance; xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:encodingStyle=http://schemas.xmlsoap.org/soap/encoding/; xmlns:xsd=http://www.w3.org/1999/XMLSchema; soapenv:Body m:SMSService dataSetVersion=1.0 xmlns:m=xmlns:m=http://www.fasfafdw.it/outboundService/SMSService; message cell=+393358478769 textMessagetestomessagio./textMessage /message /m:SMSService /soapenv:Body /soapenv:Envelope -- View this message in context: http://www.nabble.com/faultstring%3EThe-endpoint-reference-%28EPR%29-for-the-Operation-not-found-is-http%3A--122.22.2.22%3A9090-outboundws-services-Outbound-and-the-WSA-Action-%3D-%3C-faultstring%3E-tf4592781.html#a13111387 Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Amila Suriarachchi, WSO2 Inc.
Re: faultstringThe endpoint reference (EPR) for the Operation not found is http://122.22.2.22:9090/outboundws/services/Outbound and the WSA Action = /faultstring
Ok... Thank you... The 'core' problem is: when i set xmlns: soapenv:Body m:outboundService xmlns:m=http://www.pippo.it/blabla/; or in the other service soapenv:Body m:SMSService xmlns:m=http://www.pippo.it/blabla/; i've the same 'OK' result... Why? Why receive i a result of failure only for outbound in the case of setting in xmlns:m=http://www.paperino.it/lalala/; for the services? I tryed to modify the wsdl... but i don't receive the right response. Is wsdl check from the engine...or what??? Who check the xmlns and how is it check?... thank you... Amila Suriarachchi wrote: how did you create these two services. here since you don't have the soapaction and the don't use the addressing the only way to find the operation is to using the body based dispatching. body based dispatching works only if all your operations has unique input element qnames. i.e if there are two operations with same input element then axis2 can not find the correct operation. Can you check for this? Amila. On 10/9/07, G71 [EMAIL PROTECTED] wrote: Hi, i've this problem with axis2: i've two services in the same wsdl but the response of one of this service is faultstringThe endpoint reference (EPR) for the Operation not found is http://172.31.4.49:9090/outboundws/services/Outbound and the WSA Action = /faultstring i've read the but i didn't found the solution: http://wso2.org/library/176 Why the response of one of this is correct and the second is not correct? The soap action is null in all this message I post the example: POST /outboundws/services/Outbound HTTP/1.0 Host: 172.31.4.49:9090 Content-Type: text/xml; charset=utf-8 Content-Length: 1432 SOAPAction: ?xml version='1.0' encoding='UTF-8'? soapenv:Envelope xmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/ xmlns:xsi=http://www.w3.org/1999/XMLSchema-instance; xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:encodingStyle=http://schemas.xmlsoap.org/soap/encoding/; xmlns:xsd=http://www.w3.org/1999/XMLSchema; soapenv:Body m:outboundService dataSetVersion=1.0 xmlns:m=http://www.fasfafdw.it/outboundService/outboundService; appuntamento bla bla bla/appuntamento /m:outboundService /soapenv:Body /soapenv:Envelope In this case the response is not correct: Instead in the call of this service is correct: POST /outboundws/services/Outbound HTTP/1.0 Host: 172.31.4.49:9090 Content-Type: text/xml; charset=utf-8 Content-Length: 654 SOAPAction: ?xml version='1.0' encoding='UTF-8'? soapenv:Envelope xmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/ xmlns:xsi=http://www.w3.org/1999/XMLSchema-instance; xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:encodingStyle=http://schemas.xmlsoap.org/soap/encoding/; xmlns:xsd=http://www.w3.org/1999/XMLSchema; soapenv:Body m:SMSService dataSetVersion=1.0 xmlns:m=xmlns:m=http://www.fasfafdw.it/outboundService/SMSService; message cell=+393358478769 textMessagetestomessagio./textMessage /message /m:SMSService /soapenv:Body /soapenv:Envelope -- View this message in context: http://www.nabble.com/faultstring%3EThe-endpoint-reference-%28EPR%29-for-the-Operation-not-found-is-http%3A--122.22.2.22%3A9090-outboundws-services-Outbound-and-the-WSA-Action-%3D-%3C-faultstring%3E-tf4592781.html#a13111387 Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Amila Suriarachchi, WSO2 Inc. -- View this message in context: http://www.nabble.com/faultstring%3EThe-endpoint-reference-%28EPR%29-for-the-Operation-not-found-is-http%3A--122.22.2.22%3A9090-outboundws-services-Outbound-and-the-WSA-Action-%3D-%3C-faultstring%3E-tf4592781.html#a13132036 Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
