Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » XML Schema Definition (XSD) » elementFormDefault="qualified"
elementFormDefault="qualified" [message #9336] Wed, 08 January 2003 14:09 Go to next message
Eclipse User
Originally posted by: carman.itc.it

Does xsd have a problem dealing with the attribute declaration
elementFormDefault="qualified" in the schema element?

I have been analysing lots (a few hundred) wsdl documents by converting
them to schema documents (see previous email) and then loading them into
xsd. Most of them load without any problems! I have noticed, however,
that those with elementFormDefault set to "qualified" produce empty schema
objects (without type definitions and element declarations).

Some examples of wsdl documents from which I was unable to load the schema:
(Note that all of these files have probably been generated automatically
using the same software package - apache axis maybe? - which could have a
bug causing all the schemas to be invalid in the same way.)

http://dotnet.cyberthink.net/computerdictionary/computerdict ionary.asmx?wsdl
http://ntg.webs.innerhost.com/RSAFunctions/RSAFuncs.asmx?WSD L
http://terraservice.net/TerraService.asmx?WSDL
http://ws2.serviceobjects.net/ev/EmailValidate.asmx?WSDL
http://www.esynaps.com/WebServices/NFLNews.asmx?WSDL

Thanks a lot for all your help,

Mark

PS. Thanks Dave for your response about resolution returning dummy types.
Please Ignore Previous Post [message #9360 is a reply to message #9336] Fri, 10 January 2003 17:29 Go to previous message
Eclipse User
Originally posted by: carman.itc.it

Dear All,

I appologise for raising doubt over XSD's ability to handle the
elementFormDefault="qualified" attribute. XSD loads schemas containing it
without any problems!

My problem was due to the apache implementation of a DOM level 3 interface
that I was using to print out the <schema> element from wsdl documents to
a file so that I could load it into XSD. I had set the imlementation
org.apache.xml.serialize.DOMWriterImpl to be namespace aware, and it was
trying to fix the missing namespaces (which I had already fixed in my
code) and was producing invalid schema documents for some WSDL docs. The
problem had nothing to do with the elementFormDefault attribute!

Sorry about that,

Mark



Mark Carman wrote:

> Does xsd have a problem dealing with the attribute declaration
> elementFormDefault="qualified" in the schema element?

> I have been analysing lots (a few hundred) wsdl documents by converting
> them to schema documents (see previous email) and then loading them into
> xsd. Most of them load without any problems! I have noticed, however,
> that those with elementFormDefault set to "qualified" produce empty schema
> objects (without type definitions and element declarations).

> Some examples of wsdl documents from which I was unable to load the schema:
> (Note that all of these files have probably been generated automatically
> using the same software package - apache axis maybe? - which could have a
> bug causing all the schemas to be invalid in the same way.)

> http://dotnet.cyberthink.net/computerdictionary/computerdict ionary.asmx?wsdl
> http://ntg.webs.innerhost.com/RSAFunctions/RSAFuncs.asmx?WSD L
> http://terraservice.net/TerraService.asmx?WSDL
> http://ws2.serviceobjects.net/ev/EmailValidate.asmx?WSDL
> http://www.esynaps.com/WebServices/NFLNews.asmx?WSDL

> Thanks a lot for all your help,

> Mark

> PS. Thanks Dave for your response about resolution returning dummy types.
Please Ignore Previous Post [message #564581 is a reply to message #9336] Fri, 10 January 2003 17:29 Go to previous message
Eclipse User
Originally posted by: carman.itc.it

Dear All,

I appologise for raising doubt over XSD's ability to handle the
elementFormDefault="qualified" attribute. XSD loads schemas containing it
without any problems!

My problem was due to the apache implementation of a DOM level 3 interface
that I was using to print out the <schema> element from wsdl documents to
a file so that I could load it into XSD. I had set the imlementation
org.apache.xml.serialize.DOMWriterImpl to be namespace aware, and it was
trying to fix the missing namespaces (which I had already fixed in my
code) and was producing invalid schema documents for some WSDL docs. The
problem had nothing to do with the elementFormDefault attribute!

Sorry about that,

Mark



Mark Carman wrote:

> Does xsd have a problem dealing with the attribute declaration
> elementFormDefault="qualified" in the schema element?

> I have been analysing lots (a few hundred) wsdl documents by converting
> them to schema documents (see previous email) and then loading them into
> xsd. Most of them load without any problems! I have noticed, however,
> that those with elementFormDefault set to "qualified" produce empty schema
> objects (without type definitions and element declarations).

> Some examples of wsdl documents from which I was unable to load the schema:
> (Note that all of these files have probably been generated automatically
> using the same software package - apache axis maybe? - which could have a
> bug causing all the schemas to be invalid in the same way.)

> http://dotnet.cyberthink.net/computerdictionary/computerdict ionary.asmx?wsdl
> http://ntg.webs.innerhost.com/RSAFunctions/RSAFuncs.asmx?WSD L
> http://terraservice.net/TerraService.asmx?WSDL
> http://ws2.serviceobjects.net/ev/EmailValidate.asmx?WSDL
> http://www.esynaps.com/WebServices/NFLNews.asmx?WSDL

> Thanks a lot for all your help,

> Mark

> PS. Thanks Dave for your response about resolution returning dummy types.
Previous Topic:elementFormDefault="qualified"
Next Topic:XSDWildcard.getNamespaceConstraint
Goto Forum:
  


Current Time: Tue Sep 23 14:42:06 GMT 2014

Powered by FUDForum. Page generated in 0.03069 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software