Here we are the client side of WSDL-based web service run by our partners/customers. This web service will allow our system to retrieve information from the partner/customer systems. So we create a WSDL with our XML schema and hand it over to a partner, because (1) the partner does not know the details of the data structures; (2) it would advantages for us to work with one WSDL/schema across all partners/customers down the road. But then this partner does copy and paste of the main contents (w/o namespace etc.) of the data structure in the XML schema into their own existing web services (with some other operations not related to us) running on SAP BusinessObject platform; and of course, the resulting web service has then a rather different interfaces (name spaces, WSDL action names, etc.) than what our WSDL+Schema expects.
We do not use BusinessObject and know nothing about its limitation, even though we expect it does the same thing as the framework we use -- Apache Axis2. In Axis2, it is pretty easy to take any WSDL+schema and generate a skeleton for one to "fill in the blank."
My question is that, in practices, who should be responsible in defining the WSDL? Is it realistic to have the service client to define the WSDL and the server side takes it and implements the service as defined? I would assume any decent WS server platform should run services defined by an arbitrary wsdl + schema imported into the system; is it a realistic expectation in practices?