The tool might be confused because the schema's assigning two prefixes to the "w3.org/2001/XMLSchema" namespace: both "xsd" in the root element.
The tool might be confused because the schema's assigning two prefixes to the "w3.org/2001/XMLSchema"" rel="nofollow">w3.org/2001/XMLSchema"" rel="nofollow">w3.org/2001/XMLSchema" namespace: both "xsd" in the root element: xmlns:xsd="w3.org/2001/XMLSchema"" rel="nofollow">w3.org/2001/XMLSchema"" rel="nofollow">w3.org/2001/XMLSchema" and the default (i.e. , no prefix) in each "schema" element: xmlns="w3.org/2001/XMLSchema"" rel="nofollow">w3.org/2001/XMLSchema"" rel="nofollow">w3.org/2001/XMLSchema" Depending on how the software handles that case, it might be coughing on it. It's something worth fixing anyway, if for no other reason than it would make the WSDL easier to read.Is better than.
Either do what Gabriel suggests or remove the xmlns:xsd declaration from the wsdl:definitions. That should work I believe. – anirvan Sep 3 '10 at 13:03.
It is my understanding that the statement must include a schemaLocation attribute. The import statement (if you truly need it) should look something like.
Thanks for the reply Kevin. When I do that I get : "WSDLException (at /wsdl:definitions/wsdl:types/schema1): faultCode=OTHER_ERROR: An error occurred trying to resolve schema referenced at 'soapenc. Xsd', relative to 'file:/C:/XAware_5.4.0.356/designer/workspace/Imaginary Corporation/CompiereService/NewWSDLFile.
Wsdl'. : This file was not found: file:/C:/XAware_5.4.0.356/designer/workspace/Imaginary Corporation/CompiereService/soapenc. Xsd: java.io.
FileNotFoundException: This file was not found: file:/C:/XAware_5.4.0.356/designer/workspace/Imaginary Corporation/CompiereService/soapenc. Xsd – Tim Feb 1 '10 at 19:35 Tim, that file (soapenc. Xsd) has to actually exist or be a reference to a valid schema.
I would actually just leave that particular import out, I don't think you need it. – Kevin Feb 1 '10 at 19:42 Thanks Kevin for pointing that out. I downloaded the soapenc.
Xsd and placed it in the required location, so that error is gone. But now, I get the error message "org.xaware.shared.util. XAwareException: The definition for the schema "w3.Org/2001/XMLSchema"; is not available in the wsdl file.
Please define it in this file or use import statement to import from other file containing the schema definition". Sorry for the trouble, but is there any way this can be fixed? – Tim Feb 1 '10 at 19:48 Can you edit your original question to provide the full trace?
– Kevin Feb 1 '10 at 19:55 Ive updated my question kevin with the error trace im getting now. – Tim Feb 1 '10 at 20:00.
It sounds to me like it might be partly an XAware issue/quirk, since as far as I'm aware, you shouldn't have to specify the schemaLocation of well-known schemas such as w3.org/2001/XMLSchema" rel="nofollow">w3.org/2001/XMLSchema with a normally-behaving tool. Perhaps you could try pointing the import location to w3.org/2001/XMLSchema" rel="nofollow">w3.org/2001/XMLSchema. Xsd and see what happens?
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.