|WSDL/XSD Editor resolves imports only by project path [message #1092238]
||Thu, 22 August 2013 13:57
| Frank Cersovsky
Registered: August 2013
Our project team uses the WSDL and XSD editor for webservice design. We divided our webservices definitions into two parts recently. One directory contains common structures and the other one contains the webservices itself. This is replicated in all stages. The file structure on the file system looks like this.|
The whole tree is versioned in one svn repository. The access rights are set for each path separate and therefore each path is its own project in eclipse. This looks like this in eclipse project explorer.
The project structure differs from the file system structure. This fine for all tools we use. The schema validator for example can validate the WSDL and XSD. But the WSDL and XSD editors can't resolve the included files.
<!-- 1. reference based on file system structure -->
<xsd:import schemaLocation="../Common/Basic.xsd" namespace="myschemas/Basic" />
<!-- 2. reference generated by XSD-editor -->
<xsd:import schemaLocation="../RepTest_Common/Basic.xsd" namespace="myschemas/Basic" />
The first import validates correctly. But the editor doesn't show the elements and messages. He can't find the Basic.xsd.
The second import works for the editor. But the validator brings a warning, because he can't find and validate the Basic.xsd. Additional problem for us the stage depended schemaLocation.
I expect the editor to behave like the validator and resolve imports based on the file system structure. Is this a bug or expected behavior of the editor? Or is there a configuration parameter?
Thanks for your help in advance.
Powered by FUDForum
. Page generated in 0.03899 seconds