Custom WSDL port locations not honored

[Boemker, Tim]

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