Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Web Tools Project (WTP) » WSDL error? XSD: The location has not been resolved
WSDL error? XSD: The location has not been resolved [message #915814] Mon, 17 September 2012 22:22 Go to next message
Eric B is currently offline Eric B
Messages: 2
Registered: September 2012
Junior Member
Hi,

I'm not sure which forum this belongs in, but am posting to WTP in the hopes that since it is WSDL related, I'm in the right place.

I just upgraded to Eclipse Juno (4.2) from Eclipse Indigo (3.7) and where my WSDL validated without any issues in Indigo, I am now getting an odd warning and error that I do not understand.

WSDL snippet (I had to point the namespace to eclipse.org in order to be allowed to post:

<wsdl:types>
    <xsd:schema 
        targetNamespace="http://www.eclipse.org/ClientServices/LendingSimulation/V1"
        xmlns:cpReq="http://www.eclipse.org/ClientServices/LendingSimulation/CalculateProfitabilityRequest" 
        xmlns:cpRes="http://www.eclipse.org/ClientServices/LendingSimulation/CalculateProfitabilityResponse" 
        xmlns:error="http://www.eclipse.org/fw/errorMgmt">

        <xsd:import namespace="http://www.eclipse.org/ClientServices/LendingSimulation/CalculateProfitabilityRequest" schemaLocation="CalculateProfitabilityRequest.xsd" />

        <xsd:element name="calculateProfitabilityRequest" type="cpReq:CalculateProfitabilityRequestType" />

    </xsd:schema>
</wsdl:types>


Juno marks the xsd:import line with the following warning:
XSD: The location 'CalculateProfitabilityRequest.xsd' has not been resolved


It then flags the xsd:element line with the following error:
XSD: Type reference 'http://www.eclipse.org/ClientServices/LendingSimulation/CalculateProfitabilityRequest#CalculateProfitabilityRequestType' is unresolved


I'm pretty stumped. Not only do I not understand what the warning or error messages mean, I do not understand why Juno is flagging this as an issue, but in Indigo there are no issues. If I ctrl-click on the schemaLocation, Eclipse opens up the associated xsd file, so it isn't an issue of Eclipse not finding the file. All XSD files validate without any errors.

I've tried cleaning the project, but it has not made any difference.

Any thoughts or suggestions appreciated!

Thanks,

Eric
Re: WSDL error? XSD: The location has not been resolved [message #917628 is a reply to message #915814] Thu, 20 September 2012 05:08 Go to previous messageGo to next message
Wolfgang Knauf is currently offline Wolfgang Knauf
Messages: 63
Registered: July 2009
Member
Hi Eric,

did you try to add the XSD file to the Eclipse XML catalog ("Preferences" => "XML" => "XML catalog") using your "namespace" value as "Key"? Does it work if it is declared there?
Maybe there is a validation error in the imported XSD, and Eclipse just cannot resolve it because of this.

Best regards

Wolfgang
Re: WSDL error? XSD: The location has not been resolved [message #917930 is a reply to message #915814] Thu, 20 September 2012 11:15 Go to previous message
Eric B is currently offline Eric B
Messages: 2
Registered: September 2012
Junior Member
Hi Wolfgang,

I've tried adding the XSDs to the XML Catalog (Schema Catalog), but it has made no difference. However, after several hours of fighting with Eclipse, I finally discovered something really strange, that I cannot understand.

I initially loaded my project via the IBM Rational Team Concert (RTC) client. If I delete the project from Eclipse, but simply load the project via Maven->Import, the WSDL validates properly. If I reassociate it to the RTC stream, then the WSDL validation fails.

I have tried to compare the project directory (including the .settings and .project files) between an instance where the WSDL validates and where it does not, but they are all identical - no differences between any of the files.

So I am utterly confused. I need to have the code associated to my RTC Stream or I won't be able to commit any changes/etc. But at the moment, the only choice I have is to disable WSDL validation, which I would rather not do if possible.

Any suggestions of things I can try would be greatly appreciated.

Thanks!

Eric
Previous Topic:WSDLReader & XML catalog for imported schemas
Next Topic:JSDT extending indexer
Goto Forum:
  


Current Time: Wed Apr 23 02:42:30 EDT 2014

Powered by FUDForum. Page generated in 0.02327 seconds