I thought that I understood that an extra trailing '/' on a namespace was a feature of the class used for XFire compatibility in Aegis. Yet here I am with an extra level of WSDL, apparently caused by an extra slash, and I don't have that class configured anywhere. I set an explicit target namespace on my service interface without the /, and all is well. Is the slash also some sort of JAX-WS-ism?
<wsdl:definitions name="NameIndex" targetNamespace="http://ws.index.rnm.basistech.com";> <wsdl:import location="http://localhost:8080/development/NameIndex?wsdl=NameIndex.wsd l" namespace="http://ws.index.rnm.basistech.com/";> </wsdl:import>
