Community
Participate
Working Groups
Editor complains about non-existing problems in complex WSDL. Severity Description Resource In Folder Location Creation Time Id 1 WS-I: (BP2102) An XML schema import element references something other than an XML schema definition: the referenced element does not have "schema" from XML namespace "http://www.w3.org/2001/XMLSchema" as root element. SOAPFrontGetShowBalanceJMS.wsdl BalanceFlat/WebContent line 4 22. tammikuuta 2006 15:52:01 74 1 WS-I: (BP2122) A wsdl:types element contained a data type definition that is not an XML schema definition. SOAPFrontGetShowBalanceJMS.wsdl BalanceFlat/WebContent line 4 22. tammikuuta 2006 15:52:01 75 1 WS-I: (BP2102) An XML schema import element references something other than an XML schema definition: the referenced element does not have "schema" from XML namespace "http://www.w3.org/2001/XMLSchema" as root element. SOAPFrontGetShowBalanceJMS.wsdl BalanceFWLS/WebContent line 4 22. tammikuuta 2006 15:57:04 76 1 WS-I: (BP2122) A wsdl:types element contained a data type definition that is not an XML schema definition. SOAPFrontGetShowBalanceJMS.wsdl BalanceFWLS/WebContent line 4 22. tammikuuta 2006 15:57:04 77
Created attachment 34483 [details] WSDL file
This is still a problem in WTP 3.0.
The WS-I validator appears to go and try to fetch schemas from these URIs http://www.openapplications.org/oagis/9 and http://www.openapplications.org/oagis/9/unqualifieddatatypes/1.1. Both these return 404 not found errors. I have tried to add entries to the XML catalog to point to local empty schemas just to confirm that this is the case and to see if the problems go away. Unfortunately it appears that the WS-I validator does not make use of the XML catalog consistenly. The code eventually makes its way to org.eclipse.wst.wsi.internal.core.xml.XMLUtils.parseXMLDocumentURL(URL, String) where it goes directly and opens a URL connection on the URI, resulting in the failure. The validator could provide more details about the fact that the actual retrieval failed. It should probably also be enhanced to use the XML catalog consistently instead of opening URL connections all over the place. I have opened bug 252889 to track the need to locate all places where the XML catalog or a similar mechanism is not used.
