ansaurus

Question

Answer 1

A:

It is my understanding that the <import/> statement must include a schemaLocation attribute. The import statement (if you truly need it) should look something like:

<import namespace="http://schemas.xmlsoap.org/soap/encoding/" schemaLocation="soapenc.xsd" />

Kevin 2010-02-01 19:21:51

Thanks for the reply Kevin. When i do that i get : "WSDLException (at /wsdl:definitions/wsdl:types/schema[1]): 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 2010-02-01 19:35:00

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 2010-02-01 19:42:02

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 "http://www.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 2010-02-01 19:48:59

Can you edit your original question to provide the full trace?

Kevin 2010-02-01 19:55:21

Ive updated my question kevin with the error trace im getting now.

Tim 2010-02-01 20:00:34

Can you also add your updated WSDL?

Kevin 2010-02-01 20:12:16

The updated WSDL : http://pastie.org/804700

Tim 2010-02-01 20:15:25

Answer 2

A:

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 http://www.w3.org/2001/XMLSchema with a normally-behaving tool.

Perhaps you could try pointing the import location to http://www.w3.org/2001/XMLSchema.xsd and see what happens?

Chad 2010-02-12 03:09:57

Answer 3

+1 A:

The tool might be confused because the schema's assigning two prefixes to the "http://www.w3.org/2001/XMLSchema" namespace: both "xsd" in the root element:

xmlns:xsd="http://www.w3.org/2001/XMLSchema"

and the default (i.e., no prefix) in each "schema" element:

xmlns="http://www.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.

<xsd:schema>

is better than

<schema targetNamespace="http://compservice.com" xmlns="http://www.w3.org/2001/XMLSchema"&gt;

Gabriel 2010-09-02 18:55:19

Either do what Gabriel suggests or remove the xmlns:xsd declaration from the wsdl:definitions. That should work i believe.

anirvan 2010-09-03 13:03:06

ansaurus

tags:

views:

answers:

Error parsing WSDL message

related questions