Re: WSDL soap-adress not correctly set by Axis2 1.0 webapp
Yes that's it. In fact I'm testing axis2 (I used 0.95 before) so I renamed the war to axis2_1.0.war. And then I get the WSDL from http://localhost:8080/axis2_1.0/services/MyService?wsdl The wsdl:service tag is wsdl:service name="MyService" wsdl:port binding="tns:MyServiceSOAP11Binding" name="MyServiceSOAP11port0" soap:address location="http://localhost:8080/axis2/services/MyService" / /wsdl:port wsdl:port binding="tns:MyServiceSOAP12Binding" name="MyServiceSOAP12port0" soap12:address location="http://localhost:8080/axis2/services/MyService" / /wsdl:port wsdl:port binding="tns:MyServiceHttpBinding" name="ClientOracleHttpport0" http:address location="http://localhost:8080/axis2/rest/MyService" / /wsdl:port /wsdl:service robert lazarski wrote : Let me try and understand. You have: http://localhost:8080/axis2/services/MyService" But now you want to create your own webapp: http://localhost:8080/myWebApp/services/MyService" Is that correct? If so, you do this via: cp axis2.war myWebApp.war ? Robert http://www.braziloutsource.com/ On 5/5/06, Sbastien Arod [EMAIL PROTECTED] wrote: When I deploy a service to Axis2 webapp The soapaddress is set by Axis2 to soap:address location="http://localhost:8080/axis2/services/MyService"/ that's fine. However if I changed Axis2 webapp name to a other name the soapaddress is still set to http://localhost:8080/axis2/services/MyService so obviously the client can't find the Service (404 Error). Is there a way to configure that or is it a bug ? Thanks Sebastien
Re: WSDL soap-adress not correctly set by Axis2 1.0 webapp
I think this a bug in Axis2 , and need to fix in next version. So pls create a JIRA so that we will not forget this. Sébastien Arod wrote: Yes that's it. In fact I'm testing axis2 (I used 0.95 before) so I renamed the war to axis2_1.0.war. And then I get the WSDL from http://localhost:8080/axis2_1.0/services/MyService?wsdl The wsdl:service tag is wsdl:service name=MyService wsdl:port binding=tns:MyServiceSOAP11Binding name=MyServiceSOAP11port0 soap:address location=http://localhost:8080/axis2/services/MyService; / /wsdl:port wsdl:port binding=tns:MyServiceSOAP12Binding name=MyServiceSOAP12port0 soap12:address location=http://localhost:8080/axis2/services/MyService; / /wsdl:port wsdl:port binding=tns:MyServiceHttpBinding name=ClientOracleHttpport0 http:address location=http://localhost:8080/axis2/rest/MyService; / /wsdl:port /wsdl:service robert lazarski wrote : Let me try and understand. You have: http://localhost:8080/axis2/services/MyService; But now you want to create your own webapp: http://localhost:8080/myWebApp/services/MyService http://localhost:8080/axis2/services/MyService Is that correct? If so, you do this via: cp axis2.war myWebApp.war ? Robert http://www.braziloutsource.com/ On 5/5/06, *Sébastien Arod* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: When I deploy a service to Axis2 webapp The soapaddress is set by Axis2 to soap:address location=http://localhost:8080/axis2/services/MyService/ that's fine. However if I changed Axis2 webapp name to a other name the soapaddress is still set to http://localhost:8080/axis2/services/MyService so obviously the client can't find the Service (404 Error). Is there a way to configure that or is it a bug ? Thanks Sebastien -- Thanks, Deepal ~Future is Open~
Re: WSDL soap-adress not correctly set by Axis2 1.0 webapp
Bug reported http://issues.apache.org/jira/browse/AXIS2-676 Deepal Jayasinghe a crit: I think this a bug in Axis2 , and need to fix in next version. So pls create a JIRA so that we will not forget this. Sbastien Arod wrote: Yes that's it. In fact I'm testing axis2 (I used 0.95 before) so I renamed the war to axis2_1.0.war. And then I get the WSDL from http://localhost:8080/axis2_1.0/services/MyService?wsdl The wsdl:service tag is wsdl:service name="MyService" wsdl:port binding="tns:MyServiceSOAP11Binding" name="MyServiceSOAP11port0" soap:address location="http://localhost:8080/axis2/services/MyService" / /wsdl:port wsdl:port binding="tns:MyServiceSOAP12Binding" name="MyServiceSOAP12port0" soap12:address location="http://localhost:8080/axis2/services/MyService" / /wsdl:port wsdl:port binding="tns:MyServiceHttpBinding" name="ClientOracleHttpport0" http:address location="http://localhost:8080/axis2/rest/MyService" / /wsdl:port /wsdl:service robert lazarski wrote : Let me try and understand. You have: http://localhost:8080/axis2/services/MyService" But now you want to create your own webapp: http://localhost:8080/myWebApp/services/MyService http://localhost:8080/axis2/services/MyService" Is that correct? If so, you do this via: cp axis2.war myWebApp.war ? Robert http://www.braziloutsource.com/ On 5/5/06, *Sbastien Arod* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: When I deploy a service to Axis2 webapp The soapaddress is set by Axis2 to soap:address location="http://localhost:8080/axis2/services/MyService"/ that's fine. However if I changed Axis2 webapp name to a other name the soapaddress is still set to http://localhost:8080/axis2/services/MyService so obviously the client can't find the Service (404 Error). Is there a way to configure that or is it a bug ? Thanks Sebastien
Re: WSDL soap-adress not correctly set by Axis2 1.0 webapp
Let me try and understand. You have: http://localhost:8080/axis2/services/MyService But now you want to create your own webapp: http://localhost:8080/myWebApp/services/MyService Is that correct? If so, you do this via: cp axis2.war myWebApp.war ? Robert http://www.braziloutsource.com/ On 5/5/06, Sébastien Arod [EMAIL PROTECTED] wrote: When I deploy a service to Axis2 webappThe soapaddress is set by Axis2 to soap:addresslocation=http://localhost:8080/axis2/services/MyService/ that's fine. However if I changed Axis2 webapp name to a other name the soapaddressis still set to http://localhost:8080/axis2/services/MyService soobviously the client can't find the Service (404 Error). Is there a way to configure that or is it a bug ?ThanksSebastien
WSDL soap-adress not correctly set by Axis2 1.0 webapp
When I deploy a service to Axis2 webapp The soapaddress is set by Axis2 to soap:address location=http://localhost:8080/axis2/services/MyService/ that's fine. However if I changed Axis2 webapp name to a other name the soapaddress is still set to http://localhost:8080/axis2/services/MyService so obviously the client can't find the Service (404 Error). Is there a way to configure that or is it a bug ? Thanks Sebastien
