For what its worth, I figured out the source of the double schema.
Although my custom Serializers were coded to use a specific namespace,
I had not updated the namespace of the type mapping in the WSDD: <typeMapping qname="list:ListKey" xmlns:list="http://localhost/List" When generateWSDL gets called, it uses the methods defined in the class beign puiblished RPC style to find the parameter types -- and for the methods which had a ListKey parameter, it was using the typeMapping which told it to use the shorter namespace. By changing the type mapping... <typeMapping qname="list:ListKey" xmlns:list="http://localhost:8081/List/services/List" ... to match what I had coded in my serializers, I was able to eliminate the second name space and keep everything in the first. I still would like to know how to change the target namespace of the whole wsdl:definitions. Regards, Brian. Brian J. Sayatovic wrote:
|
- WSDL definitions targetNamespace vs. schema(s) targetNa... Brian J. Sayatovic
- Re: WSDL definitions targetNamespace vs. schema(s)... Brian J. Sayatovic
- Re: WSDL definitions targetNamespace vs. schema(s)... Brian J. Sayatovic
- Re: WSDL definitions targetNamespace vs. schem... tony . q . weddle