Broken after Ubuntu 9.04->9.10 upgrade [message #496273] |
Mon, 09 November 2009 15:00 |
Steve Cohen Messages: 46 Registered: July 2009 |
Member |
|
|
I upgraded a system from Ubuntu 9.04 to 9.10. This system previously ran Eclipse-Ganymede, downloaded from Eclipse, not the Ubuntu-provided version. Everything ran fine until the upgrade.
Now I find, upon opening my workspace, that there are validation errors that I can't solve. All of these errors appear in WSDL files which import XSD schemas. These schemas are located in the same directory.
The import statements take the form
<wsdl:import namespace="http://www.provider.com/path_to_wsdl"
location="schema.xsd"/>
What could possibly be broken and how might I fix it? I don't have a clue.
[Updated on: Mon, 09 November 2009 15:01] Report message to a moderator
|
|
|
|
Re: Broken after Ubuntu 9.04->9.10 upgrade [message #496413 is a reply to message #496400] |
Mon, 09 November 2009 22:41 |
Steve Cohen Messages: 46 Registered: July 2009 |
Member |
|
|
Thanks for responding, Valentin.
This is not my WSDL or XSD, they come from a Vendor.
Until I upgraded Ubuntu I never saw these errors. Now I see them. I'm not sure what more detail you want but I will try to oblige.
There is a WARNING on every such WSDL import in my workspace.
For example, this import statement
<wsdl:import namespace="http://www.provider.com/path_to_wsdl"
location="schema.xsd"/>
produces this warning.
The 'schema.xsd' document could not be imported. Check that the document exists and that the location is correct.
Following this, every reference to the schema has an error.
For example:
<wsdl:message name="Request">
<wsdl:part name="body" element="xyz:Request"/>
</wsdl:message>
(and yes, the xyz namespace has been defined previously)
produces this error:
The part 'body' has an invalid value 'BatchRequest' defined for its element. Element declarations must refer to valid values defined in a schema.
Of course. It couldn't find the schema in the warning so now it doesn't know what to do with elements referenced there.
The problem is that the Eclipse validator for some reason does not understand that it has to look in the file system in the same directory as the wsdl is located to find the schema. Or if it does know where to look, it isn't finding it.
What could possibly cause this brain-deadness on the part of the wsdl validator? This was never a problem prior to the ugrade of the system.
It is interesting that this is ONLY a problem in the WSDL validator. All the other Eclipse components, java compiler,etc., continue to work as expected.
Where do I even BEGIN to look?
I guess I'm asking is what help the validator requires from the OS to help it resolve import statements? What could possibly have changed in the OS to make such a simple operation fail? If you can tell me that, I may be able to see what else I need to do, package to import, etc. into the OS so that this will not happen.
[Updated on: Mon, 09 November 2009 22:52] Report message to a moderator
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.04028 seconds