The part that .Net seems to have a problem with is the 'nested' complex types. In the WSDL under the main element is UserAuthentication, if I break out and define UserAuthentication as an element at the top, and then declare the element as a 'UserAuthentication' type, then it imports. It basically (seems) like it doesnt like those nested elements being defined inside another one. It wants it to be defined 'at the top level'. I have yet to find another wsdl that defines elements like this, so thats why I was thinking it was a problem with the wsdl on the server end.
Tim -- View this message in context: http://www.nabble.com/Types-must-be-declared-at-the-top-level-in-the-schema-t1608831.html#a4363146 Sent from the Axis - User forum at Nabble.com.
