Thanks for the answers... but
the intension is to have all xsd togehter, and all addressed relativly (in the resource directory).
We want to deliver the interface files to our customer together with a simple installation hint like "put them in your resource directory".
What is necessary now and what we do not like is that customer has to edit our files.
This format is supported by the standard, as well as by some other tools. The problem is linked to SOAUI - so I do not know a better a forum.
As I tried to explain above: for sure we could take a different absolute path - but any absolute path is local, and somebody has to edit the delivered files. That is why we are searching for a way to address it relativly.
I can able to understand your situation! But, I'm still not sure whether Schema location can be specified with a realtive path. I would suggest you to make use of the absolute path (with the options specified in my past answer) where ever you feel comfortable to edit. Also, I came across this thread - http://stackoverflow.com/questions/1071849/is-there-an-elegant-way-to-specify-an-xsd-schemalocation-attribute-in-visual-stu ; where the have used as below relative path format,
<xs:include schemaLocation="../../ReferencedProject/Data/ReferencedSchema.xsd" />
Please check whether this solution gives hands to your problem!
Thanks,
Samy
Did my reply answer your question? Give Kudos or Accept it as a Solution to help others, Thanks. ↓↓↓
