Re: Types must be declared at the top level in the schema

[Anne Thomas Manes]

What version of .NET are you using? I wasn't aware that it had a requirement that all types be named. Certainly having named types makes it easier to do type <--> class conversions, but it shouldn't be a requirement. Anonymous types are pretty common in industry standard schemas. But it's always a good idea to name the types.

Anne

On 5/12/06, tanascar <[EMAIL PROTECTED]> wrote:

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.