Bug 247449

Description Iliyan Dimov 2008-09-16 09:44:57 EDT

+++ This bug was initially created as a clone of Bug #241504 +++

Created an attachment (id=107899)
Xsd file

Build ID: M20080221-1800

Steps To Reproduce:
1. Import or create an XSD (See attachments).
2. Include inside the XSD file the import clause(s) :

<schema>
<import namespace="http://www.w3.org/2002/06/soap-encoding"/>
<complexType> ...
</complexType>
...

</schema>
 
3. Right Click on XSD file > Validate.
   The Validation goes successfully and there are any warning markers (!) in XSD Editor. 
   This is not the expected behaviour, because the XML Catalog page does not contains 
   path to the XSD file for the given namespace : "http://www.w3.org/2002/06/soap-encoding".

Optional Steps:  

4. Open preference page from Web and XML > XML Catalog and add the xsd file  
   for the "http://www.w3.org/2002/06/soap-encoding" namespace (take it from the URL : 
   http://www.w3.org/2002/06/soap-encoding, save it inside workspace as soap_encoding.xsd).
 
5. Right Click on XSD file > Validate 
   The validation says no problem.

6. Rename the soap_encoding.xsd file to soap_encoding_.xsd file. 
   By doing this, the XML catalog will not be able to find the xsd file during the validation. 
   Now when you (Right Click on XSD file > Validate) there will be a warning marker 
   on the open xsd file, close to the place where the file is imported.

7. The problems is that XSD Validator shows warnings only for the xsd namespaces that are inside 
   XML Catalog. For all other it silently ignores thems (instead of showing warningn marker). The XSD editor works just fine for 
   "import" elements that contains @schemaLocation attribute. 


More information:
If you open the wsdl file (see attachments) you will see that it refers to the xsd file (see attachment). 
When you Right Click on wsdl file > Validate you will see that it shows an error saying that XSD is not valid. 
It turns out that wsdl validator validates xsd inside the wsdl better that the xsd validator.