Binding support for the "any" element.

Discussion in 'ASP .Net Web Services' started by TimB, Jan 28, 2009.

  1. TimB

    TimB Guest

    I have a schema that is using an "any" element that has a namespace="##other"
    and processContents="lax". When I generate VB classes from this schema
    using xsd.exe and use them in a web service, the WSDL that is produced does
    has lost these 2 attributes on that element. This causes the WSDL to not
    be a valid WSDL file because it causes some elements to be ambiguous. The
    following page from MSDN seems to state that this is how it is designed to
    work:

    http://msdn.microsoft.com/en-us/library/2w8zbwa2(VS.80).aspx

    Is this considered a problem? Are there better ways to generate classes
    from a schema for use in a web service?
    TimB, Jan 28, 2009
    #1
    1. Advertising

Want to reply to this thread or ask your own question?

It takes just 2 minutes to sign up (and it's free!). Just click the sign up button to choose a username and then you can ask your own questions on the forum.
Similar Threads
  1. Jordan
    Replies:
    2
    Views:
    2,513
    Jordan
    Feb 10, 2004
  2. CJ
    Replies:
    0
    Views:
    731
  3. Amit
    Replies:
    6
    Views:
    13,739
    Assimalyst
    Oct 24, 2006
  4. Replies:
    2
    Views:
    839
    Kevin Grover
    Oct 20, 2006
  5. HANM
    Replies:
    2
    Views:
    684
    Joseph Kesselman
    Jan 29, 2008
Loading...

Share This Page