Yes I got the same a workaround could be changing the namespace in this way
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap12/"; xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"; it works.. sounds a bit quick and dirty as well..but in the mean time, I think I`ll use it.. Boemker, Tim wrote: > > I have deployed an AAR with WSDL like this: > > <wsdl:service name="FoobarService"> > <wsdl:port name="FoobarServiceSOAP11port_http" > binding="axis2:FoobarServiceSOAP11Binding"> > <soap:address > location="http://foobar.com/FoobarService"/> > </wsdl:port> > <wsdl:port name="FoobarServiceSOAP12port_http" > binding="axis2:FoobarServiceSOAP12Binding"> > <soap12:address > location="http://foobar.com/FoobarService"/> > </wsdl:port> > <wsdl:port name="FoobarServiceHttpport1" > binding="axis2:FoobarServiceHttpBinding"> > <http:address > location="http://foobar.com/FoobarService"/> > </wsdl:port> > </wsdl:service> > > When I query Axis2 for the wsdl, it returns WSDL like this: > > <wsdl:service name="FoobarService"> > <wsdl:port name="FoobarServiceSOAP12port_http" > binding="axis2:FoobarServiceSOAP12Binding"> > <soap12:address > location="http://foobar.com/FoobarService"/> > </wsdl:port> > <wsdl:port name="FoobarServiceHttpport1" > binding="axis2:FoobarServiceHttpBinding"> > <http:address > location="http://foobar.com/FoobarService"/> > </wsdl:port> > <wsdl:port name="FoobarServiceSOAP11port_http" > binding="axis2:FoobarServiceSOAP11Binding"> > <soap:address > location="http://199.16.40.1:80/axis2/services/FoobarService"/> > </wsdl:port> > </wsdl:service> > > Why does it change the location for the SOAP 1.1 port? > > Thanks, > > Tim > > > -- View this message in context: http://www.nabble.com/Custom-WSDL-port-locations-not-honored-tf2948145.html#a11428808 Sent from the Axis - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
