Binding support for the "any" element.



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

Is this considered a problem? Are there better ways to generate classes
from a schema for use in a web service?


Ask a Question

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

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question