Home » Archived » XML Schema Definition (XSD) » Imported schema not resolved in wsdl
| |
| Re: Imported schema not resolved in wsdl [message #36663 is a reply to message #36630] |
Thu, 29 January 2004 14:37   |
 No real name
Messages: 121
Registered: July 2009 |
Senior Member |
|
|
Whoops ---
I spoke too soon - it looks like a problem, after all.
I am able to create a model using the imported schema.
However, when that same schema is imported by the wsdl file, the error
message, "location not resolved", occurs and a model is not produced.
Any suggestions?
Thanks, chris
Chris Giblin wrote:
> Hello,
> I just realized that the imported schema itself imports a schema
> location which is not resolvable.
>
> Consider this problem closed!
>
> Thaks, chris
>
>
>
> Chris Giblin wrote:
>
>> Hello,
>>
>> I am trying to produce a genmodel from wsdl using the latest emf/xsd
>> release and am receiving an unexpected error.
>>
>> I try to create a model using :
>> New > EMF Models > Load from XML Schema
>>
>> Specifying my wsdl file as input, I receive the following error:
>>
>> Problems were detected while validating and converting the XML Schemas
>> Warning: XSD: The location 'http://schemas.xmlsoap.org/abc' has not
>> been resolved : URI platform:/resource/myproject/xsd/abc.wsdl Line 46
>> Column 10
>>
>> The offending statement is the xs:import shown below with URI's
>> obfuscated:
>>
>> <wsdl:types>
>> <xs:schema>
>> <xs:import namespace="http://schemas.xmlsoap.org/abc"
>> schemaLocation="http://schemas.xmlsoap.org/abc"/>
>> </xs:schema>
>> </wsdl:types>
>>
>> With a web browser, I am indeed able to retrieve the troublesome
>> schema, so I am sure the spec is OK. When then the error message,
>> "location .. has not been resolved"?
>>
>> The eclipse log contains no related entries.
>> Eclipse is started with :
>> -Djava.endorsed.dirs=plugins/org.apache.xerces_4.0.13
>>
>> My versions:
>> java.fullversion=J2RE 1.4.0 IBM Windows 32 build cn140-20020902
>> Eclipse: 3.0.0 Build id: 200401281649
>> EMF 2.0 20040127_1738SL
>> XSD 2.0 20040127_1738SL
>>
>>
>> What am I overlooking?
>>
>> Thanks, chris
>>
|
|
|
| Re: Imported schema not resolved in wsdl [message #36697 is a reply to message #36663] |
Thu, 29 January 2004 16:17 |
Eclipse User |
|
|
|
Originally posted by: merks.ca.ibm.com
--------------84ECD51CFA70FCBB9E0E9730
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Chris,
The XSD model resolves imports on demand so if no name from the imported
namespace is referenced, the import will not be resolved. In that case the
model produces a warning message (not an error message); this is very similar
to the unused import warning you get for a in a .java file in Eclipse.
For the particular example below, it would be just as well to generate
directly from the schema; you an enter a URL directly into the import
wizard...
Chris Giblin wrote:
> Whoops ---
>
> I spoke too soon - it looks like a problem, after all.
> I am able to create a model using the imported schema.
> However, when that same schema is imported by the wsdl file, the error
> message, "location not resolved", occurs and a model is not produced.
>
> Any suggestions?
>
> Thanks, chris
>
> Chris Giblin wrote:
> > Hello,
> > I just realized that the imported schema itself imports a schema
> > location which is not resolvable.
> >
> > Consider this problem closed!
> >
> > Thaks, chris
> >
> >
> >
> > Chris Giblin wrote:
> >
> >> Hello,
> >>
> >> I am trying to produce a genmodel from wsdl using the latest emf/xsd
> >> release and am receiving an unexpected error.
> >>
> >> I try to create a model using :
> >> New > EMF Models > Load from XML Schema
> >>
> >> Specifying my wsdl file as input, I receive the following error:
> >>
> >> Problems were detected while validating and converting the XML Schemas
> >> Warning: XSD: The location 'http://schemas.xmlsoap.org/abc' has not
> >> been resolved : URI platform:/resource/myproject/xsd/abc.wsdl Line 46
> >> Column 10
> >>
> >> The offending statement is the xs:import shown below with URI's
> >> obfuscated:
> >>
> >> <wsdl:types>
> >> <xs:schema>
> >> <xs:import namespace="http://schemas.xmlsoap.org/abc"
> >> schemaLocation="http://schemas.xmlsoap.org/abc"/>
> >> </xs:schema>
> >> </wsdl:types>
> >>
> >> With a web browser, I am indeed able to retrieve the troublesome
> >> schema, so I am sure the spec is OK. When then the error message,
> >> "location .. has not been resolved"?
> >>
> >> The eclipse log contains no related entries.
> >> Eclipse is started with :
> >> -Djava.endorsed.dirs=plugins/org.apache.xerces_4.0.13
> >>
> >> My versions:
> >> java.fullversion=J2RE 1.4.0 IBM Windows 32 build cn140-20020902
> >> Eclipse: 3.0.0 Build id: 200401281649
> >> EMF 2.0 20040127_1738SL
> >> XSD 2.0 20040127_1738SL
> >>
> >>
> >> What am I overlooking?
> >>
> >> Thanks, chris
> >>
--------------84ECD51CFA70FCBB9E0E9730
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit
<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
Chris,
<p>The XSD model resolves imports on demand so if no name from the imported
namespace is referenced, the import will not be resolved. In that
case the model produces a warning message (not an error message); this
is very similar to the unused import warning you get for a in a .java file
in Eclipse.
<p>For the particular example below, it would be just as well to generate
directly from the schema; you an enter a URL directly into the import wizard...
<br>
<p>Chris Giblin wrote:
<blockquote TYPE=CITE>Whoops ---
<p>I spoke too soon - it looks like a problem, after all.
<br>I am able to create a model using the imported schema.
<br>However, when that same schema is imported by the wsdl file, the error
<br>message, "location not resolved", occurs and a model is not produced.
<p>Any suggestions?
<p>Thanks, chris
<p>Chris Giblin wrote:
<br>> Hello,
<br>> I just realized that the imported schema itself imports a schema
<br>> location which is not resolvable.
<br>>
<br>> Consider this problem closed!
<br>>
<br>> Thaks, chris
<br>>
<br>>
<br>>
<br>> Chris Giblin wrote:
<br>>
<br>>> Hello,
<br>>>
<br>>> I am trying to produce a genmodel from wsdl using the latest emf/xsd
<br>>> release and am receiving an unexpected error.
<br>>>
<br>>> I try to create a model using :
<br>>> New > EMF Models > Load from XML Schema
<br>>>
<br>>> Specifying my wsdl file as input, I receive the following error:
<br>>>
<br>>> Problems were detected while validating and converting the XML Schemas
<br>>> Warning: XSD: The location '<a href="http://schemas.xmlsoap.org/abc">http://schemas.xmlsoap.org/abc</a>'
has not
<br>>> been resolved : URI platform:/resource/myproject/xsd/abc.wsdl Line
46
<br>>> Column 10
<br>>>
<br>>> The offending statement is the xs:import shown below with URI's
<br>>> obfuscated:
<br>>>
<br>>> <wsdl:types>
<br>>> <xs:schema>
<br>>> <xs:import namespace="<a href="http://schemas.xmlsoap.org/abc">http://schemas.xmlsoap.org/abc</a>"
<br>>>
schemaLocation="<a href="http://schemas.xmlsoap.org/abc" /">http://schemas.xmlsoap.org/abc"/</a>>
<br>>> </xs:schema>
<br>>> </wsdl:types>
<br>>>
<br>>> With a web browser, I am indeed able to retrieve the troublesome
<br>>> schema, so I am sure the spec is OK. When then the error message,
<br>>> "location .. has not been resolved"?
<br>>>
<br>>> The eclipse log contains no related entries.
<br>>> Eclipse is started with :
<br>>> -Djava.endorsed.dirs=plugins/org.apache.xerces_4.0.13
<br>>>
<br>>> My versions:
<br>>> java.fullversion=J2RE 1.4.0 IBM Windows 32 build cn140-20020902
<br>>> Eclipse: 3.0.0 Build id: 200401281649
<br>>> EMF 2.0 20040127_1738SL
<br>>> XSD 2.0 20040127_1738SL
<br>>>
<br>>>
<br>>> What am I overlooking?
<br>>>
<br>>> Thanks, chris
<br>>></blockquote>
</html>
--------------84ECD51CFA70FCBB9E0E9730--
|
|
|
| Re: Imported schema not resolved in wsdl [message #36731 is a reply to message #36697] |
Thu, 29 January 2004 16:46 |
No real name
Messages: 121
Registered: July 2009 |
Senior Member |
|
|
Ed,
Thanks for the response.
But this warning prevents the genmodel from being created. So it seems
like a warning with error behavour ..
-chris
Ed Merks wrote:
> Chris,
>
> The XSD model resolves imports on demand so if no name from the imported
> namespace is referenced, the import will not be resolved. In that case
> the model produces a warning message (not an error message); this is
> very similar to the unused import warning you get for a in a .java file
> in Eclipse.
>
> For the particular example below, it would be just as well to generate
> directly from the schema; you an enter a URL directly into the import
> wizard...
>
>
> Chris Giblin wrote:
>
>> Whoops ---
>>
>> I spoke too soon - it looks like a problem, after all.
>> I am able to create a model using the imported schema.
>> However, when that same schema is imported by the wsdl file, the error
>> message, "location not resolved", occurs and a model is not produced.
>>
>> Any suggestions?
>>
>> Thanks, chris
>>
>> Chris Giblin wrote:
>> > Hello,
>> > I just realized that the imported schema itself imports a schema
>> > location which is not resolvable.
>> >
>> > Consider this problem closed!
>> >
>> > Thaks, chris
>> >
>> >
>> >
>> > Chris Giblin wrote:
>> >
>> >> Hello,
>> >>
>> >> I am trying to produce a genmodel from wsdl using the latest emf/xsd
>> >> release and am receiving an unexpected error.
>> >>
>> >> I try to create a model using :
>> >> New > EMF Models > Load from XML Schema
>> >>
>> >> Specifying my wsdl file as input, I receive the following error:
>> >>
>> >> Problems were detected while validating and converting the XML Schemas
>> >> Warning: XSD: The location 'http://schemas.xmlsoap.org/abc' has not
>> >> been resolved : URI platform:/resource/myproject/xsd/abc.wsdl Line 46
>> >> Column 10
>> >>
>> >> The offending statement is the xs:import shown below with URI's
>> >> obfuscated:
>> >>
>> >> <wsdl:types>
>> >> <xs:schema>
>> >> <xs:import namespace="http://schemas.xmlsoap.org/abc"
>> >> schemaLocation="http://schemas.xmlsoap.org/abc"/
>> <http://schemas.xmlsoap.org/abc>>
>> >> </xs:schema>
>> >> </wsdl:types>
>> >>
>> >> With a web browser, I am indeed able to retrieve the troublesome
>> >> schema, so I am sure the spec is OK. When then the error message,
>> >> "location .. has not been resolved"?
>> >>
>> >> The eclipse log contains no related entries.
>> >> Eclipse is started with :
>> >> -Djava.endorsed.dirs=plugins/org.apache.xerces_4.0.13
>> >>
>> >> My versions:
>> >> java.fullversion=J2RE 1.4.0 IBM Windows 32 build cn140-20020902
>> >> Eclipse: 3.0.0 Build id: 200401281649
>> >> EMF 2.0 20040127_1738SL
>> >> XSD 2.0 20040127_1738SL
>> >>
>> >>
>> >> What am I overlooking?
>> >>
>> >> Thanks, chris
>> >>
>>
|
|
|
| Re: Imported schema not resolved in wsdl [message #36765 is a reply to message #36731] |
Thu, 29 January 2004 18:43 |
| Eclipse User |
|
|
|
Originally posted by: merks.ca.ibm.com
--------------834EA5260D5230F8E14A6BDB
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Chris,
Yes, I'm not unsympathetic. Unfortunately the XML Schema spec leaves the
details of how to handle imports to the discretion of the processor and the
demand load behavior is well defined and correct. When I sought guidance on
this issue, pointing out that resolving or not resolving an import could change
the validity of a schema (via element substitution group additions that can
cause UPA violations), I was not able to get a definitive statement. :-(
Since the import wizard lets you specific XSD/WSDL URLs directly and lets you
specify more than one, including the additional schema's URI directly during the
import is a pretty easy "workaround". The only other alternative is to support
different import processing styles in XSD, but that's not a trivial thing to
support (though not all that difficult either).
Chris Giblin wrote:
> Ed,
> Thanks for the response.
>
> But this warning prevents the genmodel from being created. So it seems
> like a warning with error behavour ..
>
> -chris
>
> Ed Merks wrote:
>
> > Chris,
> >
> > The XSD model resolves imports on demand so if no name from the imported
> > namespace is referenced, the import will not be resolved. In that case
> > the model produces a warning message (not an error message); this is
> > very similar to the unused import warning you get for a in a .java file
> > in Eclipse.
> >
> > For the particular example below, it would be just as well to generate
> > directly from the schema; you an enter a URL directly into the import
> > wizard...
> >
> >
> > Chris Giblin wrote:
> >
> >> Whoops ---
> >>
> >> I spoke too soon - it looks like a problem, after all.
> >> I am able to create a model using the imported schema.
> >> However, when that same schema is imported by the wsdl file, the error
> >> message, "location not resolved", occurs and a model is not produced.
> >>
> >> Any suggestions?
> >>
> >> Thanks, chris
> >>
> >> Chris Giblin wrote:
> >> > Hello,
> >> > I just realized that the imported schema itself imports a schema
> >> > location which is not resolvable.
> >> >
> >> > Consider this problem closed!
> >> >
> >> > Thaks, chris
> >> >
> >> >
> >> >
> >> > Chris Giblin wrote:
> >> >
> >> >> Hello,
> >> >>
> >> >> I am trying to produce a genmodel from wsdl using the latest emf/xsd
> >> >> release and am receiving an unexpected error.
> >> >>
> >> >> I try to create a model using :
> >> >> New > EMF Models > Load from XML Schema
> >> >>
> >> >> Specifying my wsdl file as input, I receive the following error:
> >> >>
> >> >> Problems were detected while validating and converting the XML Schemas
> >> >> Warning: XSD: The location 'http://schemas.xmlsoap.org/abc' has not
> >> >> been resolved : URI platform:/resource/myproject/xsd/abc.wsdl Line 46
> >> >> Column 10
> >> >>
> >> >> The offending statement is the xs:import shown below with URI's
> >> >> obfuscated:
> >> >>
> >> >> <wsdl:types>
> >> >> <xs:schema>
> >> >> <xs:import namespace="http://schemas.xmlsoap.org/abc"
> >> >> schemaLocation="http://schemas.xmlsoap.org/abc"/
> >> <http://schemas.xmlsoap.org/abc>>
> >> >> </xs:schema>
> >> >> </wsdl:types>
> >> >>
> >> >> With a web browser, I am indeed able to retrieve the troublesome
> >> >> schema, so I am sure the spec is OK. When then the error message,
> >> >> "location .. has not been resolved"?
> >> >>
> >> >> The eclipse log contains no related entries.
> >> >> Eclipse is started with :
> >> >> -Djava.endorsed.dirs=plugins/org.apache.xerces_4.0.13
> >> >>
> >> >> My versions:
> >> >> java.fullversion=J2RE 1.4.0 IBM Windows 32 build cn140-20020902
> >> >> Eclipse: 3.0.0 Build id: 200401281649
> >> >> EMF 2.0 20040127_1738SL
> >> >> XSD 2.0 20040127_1738SL
> >> >>
> >> >>
> >> >> What am I overlooking?
> >> >>
> >> >> Thanks, chris
> >> >>
> >>
--------------834EA5260D5230F8E14A6BDB
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit
<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
Chris,
<p>Yes, I'm not unsympathetic. Unfortunately the XML Schema spec
leaves the details of how to handle imports to the discretion of the processor
and the demand load behavior is well defined and correct. When I
sought guidance on this issue, pointing out that resolving or not resolving
an import could change the validity of a schema (via element substitution
group additions that can cause UPA violations), I was not able to get a
definitive statement. :-(
<p>Since the import wizard lets you specific XSD/WSDL URLs directly and
lets you specify more than one, including the additional schema's URI directly
during the import is a pretty easy "workaround". The only other alternative
is to support different import processing styles in XSD, but that's not
a trivial thing to support (though not all that difficult either).
<br>
<p>Chris Giblin wrote:
<blockquote TYPE=CITE>Ed,
<br>Thanks for the response.
<p>But this warning prevents the genmodel from being created. So it seems
<br>like a warning with error behavour ..
<p>-chris
<p>Ed Merks wrote:
<p>> Chris,
<br>>
<br>> The XSD model resolves imports on demand so if no name from the imported
<br>> namespace is referenced, the import will not be resolved. In
that case
<br>> the model produces a warning message (not an error message); this
is
<br>> very similar to the unused import warning you get for a in a .java
file
<br>> in Eclipse.
<br>>
<br>> For the particular example below, it would be just as well to generate
<br>> directly from the schema; you an enter a URL directly into the import
<br>> wizard...
<br>>
<br>>
<br>> Chris Giblin wrote:
<br>>
<br>>> Whoops ---
<br>>>
<br>>> I spoke too soon - it looks like a problem, after all.
<br>>> I am able to create a model using the imported schema.
<br>>> However, when that same schema is imported by the wsdl file, the
error
<br>>> message, "location not resolved", occurs and a model is not produced.
<br>>>
<br>>> Any suggestions?
<br>>>
<br>>> Thanks, chris
<br>>>
<br>>> Chris Giblin wrote:
<br>>> > Hello,
<br>>> > I just realized that the imported schema itself imports a schema
<br>>> > location which is not resolvable.
<br>>> >
<br>>> > Consider this problem closed!
<br>>> >
<br>>> > Thaks, chris
<br>>> >
<br>>> >
<br>>> >
<br>>> > Chris Giblin wrote:
<br>>> >
<br>>> >> Hello,
<br>>> >>
<br>>> >> I am trying to produce a genmodel from wsdl using the latest
emf/xsd
<br>>> >> release and am receiving an unexpected error.
<br>>> >>
<br>>> >> I try to create a model using :
<br>>> >> New > EMF Models > Load from XML Schema
<br>>> >>
<br>>> >> Specifying my wsdl file as input, I receive the following error:
<br>>> >>
<br>>> >> Problems were detected while validating and converting the XML
Schemas
<br>>> >> Warning: XSD: The location '<a href="http://schemas.xmlsoap.org/abc">http://schemas.xmlsoap.org/abc</a>'
has not
<br>>> >> been resolved : URI platform:/resource/myproject/xsd/abc.wsdl
Line 46
<br>>> >> Column 10
<br>>> >>
<br>>> >> The offending statement is the xs:import shown below with URI's
<br>>> >> obfuscated:
<br>>> >>
<br>>> >> <wsdl:types>
<br>>> >> <xs:schema>
<br>>> >> <xs:import namespace="<a href="http://schemas.xmlsoap.org/abc">http://schemas.xmlsoap.org/abc</a>"
<br>>> >>
schemaLocation="<a href="http://schemas.xmlsoap.org/abc" /">http://schemas.xmlsoap.org/abc"/</a>
<br>>> <<a href="http://schemas.xmlsoap.org/abc">http://schemas.xmlsoap.org/abc</a>>>
<br>>> >> </xs:schema>
<br>>> >> </wsdl:types>
<br>>> >>
<br>>> >> With a web browser, I am indeed able to retrieve the troublesome
<br>>> >> schema, so I am sure the spec is OK. When then the error message,
<br>>> >> "location .. has not been resolved"?
<br>>> >>
<br>>> >> The eclipse log contains no related entries.
<br>>> >> Eclipse is started with :
<br>>> >> -Djava.endorsed.dirs=plugins/org.apache.xerces_4.0.13
<br>>> >>
<br>>> >> My versions:
<br>>> >> java.fullversion=J2RE 1.4.0 IBM Windows 32 build
cn140-20020902
<br>>> >> Eclipse: 3.0.0 Build id: 200401281649
<br>>> >> EMF 2.0 20040127_1738SL
<br>>> >> XSD 2.0 20040127_1738SL
<br>>> >>
<br>>> >>
<br>>> >> What am I overlooking?
<br>>> >>
<br>>> >> Thanks, chris
<br>>> >>
<br>>></blockquote>
</html>
--------------834EA5260D5230F8E14A6BDB--
|
|
|
| Re: Imported schema not resolved in wsdl [message #36968 is a reply to message #36765] |
Fri, 30 January 2004 13:52 |
No real name
Messages: 121
Registered: July 2009 |
Senior Member |
|
|
Ed,
I was aware of the ability to specify multiple xsd/wsdl file and URI's
and used this. But the whole thing "fails" because of the single
troublesome wsdl file's import. The solution was to remove the wsdl
file, which in this case caused no problems.
Thanks, chris
Ed Merks wrote:
> Chris,
>
> Yes, I'm not unsympathetic. Unfortunately the XML Schema spec leaves
> the details of how to handle imports to the discretion of the processor
> and the demand load behavior is well defined and correct. When I sought
> guidance on this issue, pointing out that resolving or not resolving an
> import could change the validity of a schema (via element substitution
> group additions that can cause UPA violations), I was not able to get a
> definitive statement. :-(
>
> Since the import wizard lets you specific XSD/WSDL URLs directly and
> lets you specify more than one, including the additional schema's URI
> directly during the import is a pretty easy "workaround". The only
> other alternative is to support different import processing styles in
> XSD, but that's not a trivial thing to support (though not all that
> difficult either).
>
>
> Chris Giblin wrote:
>
>> Ed,
>> Thanks for the response.
>>
>> But this warning prevents the genmodel from being created. So it seems
>> like a warning with error behavour ..
>>
>> -chris
>>
>> Ed Merks wrote:
>>
>> > Chris,
>> >
>> > The XSD model resolves imports on demand so if no name from the
>> imported
>> > namespace is referenced, the import will not be resolved. In that case
>> > the model produces a warning message (not an error message); this is
>> > very similar to the unused import warning you get for a in a .java file
>> > in Eclipse.
>> >
>> > For the particular example below, it would be just as well to generate
>> > directly from the schema; you an enter a URL directly into the import
>> > wizard...
>> >
>> >
>> > Chris Giblin wrote:
>> >
>> >> Whoops ---
>> >>
>> >> I spoke too soon - it looks like a problem, after all.
>> >> I am able to create a model using the imported schema.
>> >> However, when that same schema is imported by the wsdl file, the error
>> >> message, "location not resolved", occurs and a model is not produced.
>> >>
>> >> Any suggestions?
>> >>
>> >> Thanks, chris
>> >>
>> >> Chris Giblin wrote:
>> >> > Hello,
>> >> > I just realized that the imported schema itself imports a schema
>> >> > location which is not resolvable.
>> >> >
>> >> > Consider this problem closed!
>> >> >
>> >> > Thaks, chris
>> >> >
>> >> >
>> >> >
>> >> > Chris Giblin wrote:
>> >> >
>> >> >> Hello,
>> >> >>
>> >> >> I am trying to produce a genmodel from wsdl using the latest
>> emf/xsd
>> >> >> release and am receiving an unexpected error.
>> >> >>
>> >> >> I try to create a model using :
>> >> >> New > EMF Models > Load from XML Schema
>> >> >>
>> >> >> Specifying my wsdl file as input, I receive the following error:
>> >> >>
>> >> >> Problems were detected while validating and converting the XML
>> Schemas
>> >> >> Warning: XSD: The location 'http://schemas.xmlsoap.org/abc'
>> has not
>> >> >> been resolved : URI platform:/resource/myproject/xsd/abc.wsdl
>> Line 46
>> >> >> Column 10
>> >> >>
>> >> >> The offending statement is the xs:import shown below with URI's
>> >> >> obfuscated:
>> >> >>
>> >> >> <wsdl:types>
>> >> >> <xs:schema>
>> >> >> <xs:import namespace="http://schemas.xmlsoap.org/abc"
>> >> >> schemaLocation="http://schemas.xmlsoap.org/abc"/
>> <http://schemas.xmlsoap.org/abc>
>> >> <http://schemas.xmlsoap.org/abc>>
>> >> >> </xs:schema>
>> >> >> </wsdl:types>
>> >> >>
>> >> >> With a web browser, I am indeed able to retrieve the troublesome
>> >> >> schema, so I am sure the spec is OK. When then the error message,
>> >> >> "location .. has not been resolved"?
>> >> >>
>> >> >> The eclipse log contains no related entries.
>> >> >> Eclipse is started with :
>> >> >> -Djava.endorsed.dirs=plugins/org.apache.xerces_4.0.13
>> >> >>
>> >> >> My versions:
>> >> >> java.fullversion=J2RE 1.4.0 IBM Windows 32 build cn140-20020902
>> >> >> Eclipse: 3.0.0 Build id: 200401281649
>> >> >> EMF 2.0 20040127_1738SL
>> >> >> XSD 2.0 20040127_1738SL
>> >> >>
>> >> >>
>> >> >> What am I overlooking?
>> >> >>
>> >> >> Thanks, chris
>> >> >>
>> >>
>>
|
|
| |
| Re: Imported schema not resolved in wsdl [message #583178 is a reply to message #36630] |
Thu, 29 January 2004 14:37 |
No real name
Messages: 121
Registered: July 2009 |
Senior Member |
|
|
Whoops ---
I spoke too soon - it looks like a problem, after all.
I am able to create a model using the imported schema.
However, when that same schema is imported by the wsdl file, the error
message, "location not resolved", occurs and a model is not produced.
Any suggestions?
Thanks, chris
Chris Giblin wrote:
> Hello,
> I just realized that the imported schema itself imports a schema
> location which is not resolvable.
>
> Consider this problem closed!
>
> Thaks, chris
>
>
>
> Chris Giblin wrote:
>
>> Hello,
>>
>> I am trying to produce a genmodel from wsdl using the latest emf/xsd
>> release and am receiving an unexpected error.
>>
>> I try to create a model using :
>> New > EMF Models > Load from XML Schema
>>
>> Specifying my wsdl file as input, I receive the following error:
>>
>> Problems were detected while validating and converting the XML Schemas
>> Warning: XSD: The location 'http://schemas.xmlsoap.org/abc' has not
>> been resolved : URI platform:/resource/myproject/xsd/abc.wsdl Line 46
>> Column 10
>>
>> The offending statement is the xs:import shown below with URI's
>> obfuscated:
>>
>> <wsdl:types>
>> <xs:schema>
>> <xs:import namespace="http://schemas.xmlsoap.org/abc"
>> schemaLocation="http://schemas.xmlsoap.org/abc"/>
>> </xs:schema>
>> </wsdl:types>
>>
>> With a web browser, I am indeed able to retrieve the troublesome
>> schema, so I am sure the spec is OK. When then the error message,
>> "location .. has not been resolved"?
>>
>> The eclipse log contains no related entries.
>> Eclipse is started with :
>> -Djava.endorsed.dirs=plugins/org.apache.xerces_4.0.13
>>
>> My versions:
>> java.fullversion=J2RE 1.4.0 IBM Windows 32 build cn140-20020902
>> Eclipse: 3.0.0 Build id: 200401281649
>> EMF 2.0 20040127_1738SL
>> XSD 2.0 20040127_1738SL
>>
>>
>> What am I overlooking?
>>
>> Thanks, chris
>>
|
|
|
| Re: Imported schema not resolved in wsdl [message #583191 is a reply to message #36663] |
Thu, 29 January 2004 16:17 |
Ed Merks
Messages: 33140
Registered: July 2009 |
Senior Member |
|
|
--------------84ECD51CFA70FCBB9E0E9730
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Chris,
The XSD model resolves imports on demand so if no name from the imported
namespace is referenced, the import will not be resolved. In that case the
model produces a warning message (not an error message); this is very similar
to the unused import warning you get for a in a .java file in Eclipse.
For the particular example below, it would be just as well to generate
directly from the schema; you an enter a URL directly into the import
wizard...
Chris Giblin wrote:
> Whoops ---
>
> I spoke too soon - it looks like a problem, after all.
> I am able to create a model using the imported schema.
> However, when that same schema is imported by the wsdl file, the error
> message, "location not resolved", occurs and a model is not produced.
>
> Any suggestions?
>
> Thanks, chris
>
> Chris Giblin wrote:
> > Hello,
> > I just realized that the imported schema itself imports a schema
> > location which is not resolvable.
> >
> > Consider this problem closed!
> >
> > Thaks, chris
> >
> >
> >
> > Chris Giblin wrote:
> >
> >> Hello,
> >>
> >> I am trying to produce a genmodel from wsdl using the latest emf/xsd
> >> release and am receiving an unexpected error.
> >>
> >> I try to create a model using :
> >> New > EMF Models > Load from XML Schema
> >>
> >> Specifying my wsdl file as input, I receive the following error:
> >>
> >> Problems were detected while validating and converting the XML Schemas
> >> Warning: XSD: The location 'http://schemas.xmlsoap.org/abc' has not
> >> been resolved : URI platform:/resource/myproject/xsd/abc.wsdl Line 46
> >> Column 10
> >>
> >> The offending statement is the xs:import shown below with URI's
> >> obfuscated:
> >>
> >> <wsdl:types>
> >> <xs:schema>
> >> <xs:import namespace="http://schemas.xmlsoap.org/abc"
> >> schemaLocation="http://schemas.xmlsoap.org/abc"/>
> >> </xs:schema>
> >> </wsdl:types>
> >>
> >> With a web browser, I am indeed able to retrieve the troublesome
> >> schema, so I am sure the spec is OK. When then the error message,
> >> "location .. has not been resolved"?
> >>
> >> The eclipse log contains no related entries.
> >> Eclipse is started with :
> >> -Djava.endorsed.dirs=plugins/org.apache.xerces_4.0.13
> >>
> >> My versions:
> >> java.fullversion=J2RE 1.4.0 IBM Windows 32 build cn140-20020902
> >> Eclipse: 3.0.0 Build id: 200401281649
> >> EMF 2.0 20040127_1738SL
> >> XSD 2.0 20040127_1738SL
> >>
> >>
> >> What am I overlooking?
> >>
> >> Thanks, chris
> >>
--------------84ECD51CFA70FCBB9E0E9730
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit
<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
Chris,
<p>The XSD model resolves imports on demand so if no name from the imported
namespace is referenced, the import will not be resolved. In that
case the model produces a warning message (not an error message); this
is very similar to the unused import warning you get for a in a .java file
in Eclipse.
<p>For the particular example below, it would be just as well to generate
directly from the schema; you an enter a URL directly into the import wizard...
<br>
<p>Chris Giblin wrote:
<blockquote TYPE=CITE>Whoops ---
<p>I spoke too soon - it looks like a problem, after all.
<br>I am able to create a model using the imported schema.
<br>However, when that same schema is imported by the wsdl file, the error
<br>message, "location not resolved", occurs and a model is not produced.
<p>Any suggestions?
<p>Thanks, chris
<p>Chris Giblin wrote:
<br>> Hello,
<br>> I just realized that the imported schema itself imports a schema
<br>> location which is not resolvable.
<br>>
<br>> Consider this problem closed!
<br>>
<br>> Thaks, chris
<br>>
<br>>
<br>>
<br>> Chris Giblin wrote:
<br>>
<br>>> Hello,
<br>>>
<br>>> I am trying to produce a genmodel from wsdl using the latest emf/xsd
<br>>> release and am receiving an unexpected error.
<br>>>
<br>>> I try to create a model using :
<br>>> New > EMF Models > Load from XML Schema
<br>>>
<br>>> Specifying my wsdl file as input, I receive the following error:
<br>>>
<br>>> Problems were detected while validating and converting the XML Schemas
<br>>> Warning: XSD: The location '<a href="http://schemas.xmlsoap.org/abc">http://schemas.xmlsoap.org/abc</a>'
has not
<br>>> been resolved : URI platform:/resource/myproject/xsd/abc.wsdl Line
46
<br>>> Column 10
<br>>>
<br>>> The offending statement is the xs:import shown below with URI's
<br>>> obfuscated:
<br>>>
<br>>> <wsdl:types>
<br>>> <xs:schema>
<br>>> <xs:import namespace="<a href="http://schemas.xmlsoap.org/abc">http://schemas.xmlsoap.org/abc</a>"
<br>>>
schemaLocation="<a href="http://schemas.xmlsoap.org/abc" /">http://schemas.xmlsoap.org/abc"/</a>>
<br>>> </xs:schema>
<br>>> </wsdl:types>
<br>>>
<br>>> With a web browser, I am indeed able to retrieve the troublesome
<br>>> schema, so I am sure the spec is OK. When then the error message,
<br>>> "location .. has not been resolved"?
<br>>>
<br>>> The eclipse log contains no related entries.
<br>>> Eclipse is started with :
<br>>> -Djava.endorsed.dirs=plugins/org.apache.xerces_4.0.13
<br>>>
<br>>> My versions:
<br>>> java.fullversion=J2RE 1.4.0 IBM Windows 32 build cn140-20020902
<br>>> Eclipse: 3.0.0 Build id: 200401281649
<br>>> EMF 2.0 20040127_1738SL
<br>>> XSD 2.0 20040127_1738SL
<br>>>
<br>>>
<br>>> What am I overlooking?
<br>>>
<br>>> Thanks, chris
<br>>></blockquote>
</html>
--------------84ECD51CFA70FCBB9E0E9730--
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
| Re: Imported schema not resolved in wsdl [message #583202 is a reply to message #36697] |
Thu, 29 January 2004 16:46 |
No real name
Messages: 121
Registered: July 2009 |
Senior Member |
|
|
Ed,
Thanks for the response.
But this warning prevents the genmodel from being created. So it seems
like a warning with error behavour ..
-chris
Ed Merks wrote:
> Chris,
>
> The XSD model resolves imports on demand so if no name from the imported
> namespace is referenced, the import will not be resolved. In that case
> the model produces a warning message (not an error message); this is
> very similar to the unused import warning you get for a in a .java file
> in Eclipse.
>
> For the particular example below, it would be just as well to generate
> directly from the schema; you an enter a URL directly into the import
> wizard...
>
>
> Chris Giblin wrote:
>
>> Whoops ---
>>
>> I spoke too soon - it looks like a problem, after all.
>> I am able to create a model using the imported schema.
>> However, when that same schema is imported by the wsdl file, the error
>> message, "location not resolved", occurs and a model is not produced.
>>
>> Any suggestions?
>>
>> Thanks, chris
>>
>> Chris Giblin wrote:
>> > Hello,
>> > I just realized that the imported schema itself imports a schema
>> > location which is not resolvable.
>> >
>> > Consider this problem closed!
>> >
>> > Thaks, chris
>> >
>> >
>> >
>> > Chris Giblin wrote:
>> >
>> >> Hello,
>> >>
>> >> I am trying to produce a genmodel from wsdl using the latest emf/xsd
>> >> release and am receiving an unexpected error.
>> >>
>> >> I try to create a model using :
>> >> New > EMF Models > Load from XML Schema
>> >>
>> >> Specifying my wsdl file as input, I receive the following error:
>> >>
>> >> Problems were detected while validating and converting the XML Schemas
>> >> Warning: XSD: The location 'http://schemas.xmlsoap.org/abc' has not
>> >> been resolved : URI platform:/resource/myproject/xsd/abc.wsdl Line 46
>> >> Column 10
>> >>
>> >> The offending statement is the xs:import shown below with URI's
>> >> obfuscated:
>> >>
>> >> <wsdl:types>
>> >> <xs:schema>
>> >> <xs:import namespace="http://schemas.xmlsoap.org/abc"
>> >> schemaLocation="http://schemas.xmlsoap.org/abc"/
>> <http://schemas.xmlsoap.org/abc>>
>> >> </xs:schema>
>> >> </wsdl:types>
>> >>
>> >> With a web browser, I am indeed able to retrieve the troublesome
>> >> schema, so I am sure the spec is OK. When then the error message,
>> >> "location .. has not been resolved"?
>> >>
>> >> The eclipse log contains no related entries.
>> >> Eclipse is started with :
>> >> -Djava.endorsed.dirs=plugins/org.apache.xerces_4.0.13
>> >>
>> >> My versions:
>> >> java.fullversion=J2RE 1.4.0 IBM Windows 32 build cn140-20020902
>> >> Eclipse: 3.0.0 Build id: 200401281649
>> >> EMF 2.0 20040127_1738SL
>> >> XSD 2.0 20040127_1738SL
>> >>
>> >>
>> >> What am I overlooking?
>> >>
>> >> Thanks, chris
>> >>
>>
|
|
|
| Re: Imported schema not resolved in wsdl [message #583215 is a reply to message #36731] |
Thu, 29 January 2004 18:43 |
Ed Merks
Messages: 33140
Registered: July 2009 |
Senior Member |
|
|
--------------834EA5260D5230F8E14A6BDB
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Chris,
Yes, I'm not unsympathetic. Unfortunately the XML Schema spec leaves the
details of how to handle imports to the discretion of the processor and the
demand load behavior is well defined and correct. When I sought guidance on
this issue, pointing out that resolving or not resolving an import could change
the validity of a schema (via element substitution group additions that can
cause UPA violations), I was not able to get a definitive statement. :-(
Since the import wizard lets you specific XSD/WSDL URLs directly and lets you
specify more than one, including the additional schema's URI directly during the
import is a pretty easy "workaround". The only other alternative is to support
different import processing styles in XSD, but that's not a trivial thing to
support (though not all that difficult either).
Chris Giblin wrote:
> Ed,
> Thanks for the response.
>
> But this warning prevents the genmodel from being created. So it seems
> like a warning with error behavour ..
>
> -chris
>
> Ed Merks wrote:
>
> > Chris,
> >
> > The XSD model resolves imports on demand so if no name from the imported
> > namespace is referenced, the import will not be resolved. In that case
> > the model produces a warning message (not an error message); this is
> > very similar to the unused import warning you get for a in a .java file
> > in Eclipse.
> >
> > For the particular example below, it would be just as well to generate
> > directly from the schema; you an enter a URL directly into the import
> > wizard...
> >
> >
> > Chris Giblin wrote:
> >
> >> Whoops ---
> >>
> >> I spoke too soon - it looks like a problem, after all.
> >> I am able to create a model using the imported schema.
> >> However, when that same schema is imported by the wsdl file, the error
> >> message, "location not resolved", occurs and a model is not produced.
> >>
> >> Any suggestions?
> >>
> >> Thanks, chris
> >>
> >> Chris Giblin wrote:
> >> > Hello,
> >> > I just realized that the imported schema itself imports a schema
> >> > location which is not resolvable.
> >> >
> >> > Consider this problem closed!
> >> >
> >> > Thaks, chris
> >> >
> >> >
> >> >
> >> > Chris Giblin wrote:
> >> >
> >> >> Hello,
> >> >>
> >> >> I am trying to produce a genmodel from wsdl using the latest emf/xsd
> >> >> release and am receiving an unexpected error.
> >> >>
> >> >> I try to create a model using :
> >> >> New > EMF Models > Load from XML Schema
> >> >>
> >> >> Specifying my wsdl file as input, I receive the following error:
> >> >>
> >> >> Problems were detected while validating and converting the XML Schemas
> >> >> Warning: XSD: The location 'http://schemas.xmlsoap.org/abc' has not
> >> >> been resolved : URI platform:/resource/myproject/xsd/abc.wsdl Line 46
> >> >> Column 10
> >> >>
> >> >> The offending statement is the xs:import shown below with URI's
> >> >> obfuscated:
> >> >>
> >> >> <wsdl:types>
> >> >> <xs:schema>
> >> >> <xs:import namespace="http://schemas.xmlsoap.org/abc"
> >> >> schemaLocation="http://schemas.xmlsoap.org/abc"/
> >> <http://schemas.xmlsoap.org/abc>>
> >> >> </xs:schema>
> >> >> </wsdl:types>
> >> >>
> >> >> With a web browser, I am indeed able to retrieve the troublesome
> >> >> schema, so I am sure the spec is OK. When then the error message,
> >> >> "location .. has not been resolved"?
> >> >>
> >> >> The eclipse log contains no related entries.
> >> >> Eclipse is started with :
> >> >> -Djava.endorsed.dirs=plugins/org.apache.xerces_4.0.13
> >> >>
> >> >> My versions:
> >> >> java.fullversion=J2RE 1.4.0 IBM Windows 32 build cn140-20020902
> >> >> Eclipse: 3.0.0 Build id: 200401281649
> >> >> EMF 2.0 20040127_1738SL
> >> >> XSD 2.0 20040127_1738SL
> >> >>
> >> >>
> >> >> What am I overlooking?
> >> >>
> >> >> Thanks, chris
> >> >>
> >>
--------------834EA5260D5230F8E14A6BDB
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit
<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
Chris,
<p>Yes, I'm not unsympathetic. Unfortunately the XML Schema spec
leaves the details of how to handle imports to the discretion of the processor
and the demand load behavior is well defined and correct. When I
sought guidance on this issue, pointing out that resolving or not resolving
an import could change the validity of a schema (via element substitution
group additions that can cause UPA violations), I was not able to get a
definitive statement. :-(
<p>Since the import wizard lets you specific XSD/WSDL URLs directly and
lets you specify more than one, including the additional schema's URI directly
during the import is a pretty easy "workaround". The only other alternative
is to support different import processing styles in XSD, but that's not
a trivial thing to support (though not all that difficult either).
<br>
<p>Chris Giblin wrote:
<blockquote TYPE=CITE>Ed,
<br>Thanks for the response.
<p>But this warning prevents the genmodel from being created. So it seems
<br>like a warning with error behavour ..
<p>-chris
<p>Ed Merks wrote:
<p>> Chris,
<br>>
<br>> The XSD model resolves imports on demand so if no name from the imported
<br>> namespace is referenced, the import will not be resolved. In
that case
<br>> the model produces a warning message (not an error message); this
is
<br>> very similar to the unused import warning you get for a in a .java
file
<br>> in Eclipse.
<br>>
<br>> For the particular example below, it would be just as well to generate
<br>> directly from the schema; you an enter a URL directly into the import
<br>> wizard...
<br>>
<br>>
<br>> Chris Giblin wrote:
<br>>
<br>>> Whoops ---
<br>>>
<br>>> I spoke too soon - it looks like a problem, after all.
<br>>> I am able to create a model using the imported schema.
<br>>> However, when that same schema is imported by the wsdl file, the
error
<br>>> message, "location not resolved", occurs and a model is not produced.
<br>>>
<br>>> Any suggestions?
<br>>>
<br>>> Thanks, chris
<br>>>
<br>>> Chris Giblin wrote:
<br>>> > Hello,
<br>>> > I just realized that the imported schema itself imports a schema
<br>>> > location which is not resolvable.
<br>>> >
<br>>> > Consider this problem closed!
<br>>> >
<br>>> > Thaks, chris
<br>>> >
<br>>> >
<br>>> >
<br>>> > Chris Giblin wrote:
<br>>> >
<br>>> >> Hello,
<br>>> >>
<br>>> >> I am trying to produce a genmodel from wsdl using the latest
emf/xsd
<br>>> >> release and am receiving an unexpected error.
<br>>> >>
<br>>> >> I try to create a model using :
<br>>> >> New > EMF Models > Load from XML Schema
<br>>> >>
<br>>> >> Specifying my wsdl file as input, I receive the following error:
<br>>> >>
<br>>> >> Problems were detected while validating and converting the XML
Schemas
<br>>> >> Warning: XSD: The location '<a href="http://schemas.xmlsoap.org/abc">http://schemas.xmlsoap.org/abc</a>'
has not
<br>>> >> been resolved : URI platform:/resource/myproject/xsd/abc.wsdl
Line 46
<br>>> >> Column 10
<br>>> >>
<br>>> >> The offending statement is the xs:import shown below with URI's
<br>>> >> obfuscated:
<br>>> >>
<br>>> >> <wsdl:types>
<br>>> >> <xs:schema>
<br>>> >> <xs:import namespace="<a href="http://schemas.xmlsoap.org/abc">http://schemas.xmlsoap.org/abc</a>"
<br>>> >>
schemaLocation="<a href="http://schemas.xmlsoap.org/abc" /">http://schemas.xmlsoap.org/abc"/</a>
<br>>> <<a href="http://schemas.xmlsoap.org/abc">http://schemas.xmlsoap.org/abc</a>>>
<br>>> >> </xs:schema>
<br>>> >> </wsdl:types>
<br>>> >>
<br>>> >> With a web browser, I am indeed able to retrieve the troublesome
<br>>> >> schema, so I am sure the spec is OK. When then the error message,
<br>>> >> "location .. has not been resolved"?
<br>>> >>
<br>>> >> The eclipse log contains no related entries.
<br>>> >> Eclipse is started with :
<br>>> >> -Djava.endorsed.dirs=plugins/org.apache.xerces_4.0.13
<br>>> >>
<br>>> >> My versions:
<br>>> >> java.fullversion=J2RE 1.4.0 IBM Windows 32 build
cn140-20020902
<br>>> >> Eclipse: 3.0.0 Build id: 200401281649
<br>>> >> EMF 2.0 20040127_1738SL
<br>>> >> XSD 2.0 20040127_1738SL
<br>>> >>
<br>>> >>
<br>>> >> What am I overlooking?
<br>>> >>
<br>>> >> Thanks, chris
<br>>> >>
<br>>></blockquote>
</html>
--------------834EA5260D5230F8E14A6BDB--
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
| Re: Imported schema not resolved in wsdl [message #583336 is a reply to message #36765] |
Fri, 30 January 2004 13:52 |
No real name
Messages: 121
Registered: July 2009 |
Senior Member |
|
|
Ed,
I was aware of the ability to specify multiple xsd/wsdl file and URI's
and used this. But the whole thing "fails" because of the single
troublesome wsdl file's import. The solution was to remove the wsdl
file, which in this case caused no problems.
Thanks, chris
Ed Merks wrote:
> Chris,
>
> Yes, I'm not unsympathetic. Unfortunately the XML Schema spec leaves
> the details of how to handle imports to the discretion of the processor
> and the demand load behavior is well defined and correct. When I sought
> guidance on this issue, pointing out that resolving or not resolving an
> import could change the validity of a schema (via element substitution
> group additions that can cause UPA violations), I was not able to get a
> definitive statement. :-(
>
> Since the import wizard lets you specific XSD/WSDL URLs directly and
> lets you specify more than one, including the additional schema's URI
> directly during the import is a pretty easy "workaround". The only
> other alternative is to support different import processing styles in
> XSD, but that's not a trivial thing to support (though not all that
> difficult either).
>
>
> Chris Giblin wrote:
>
>> Ed,
>> Thanks for the response.
>>
>> But this warning prevents the genmodel from being created. So it seems
>> like a warning with error behavour ..
>>
>> -chris
>>
>> Ed Merks wrote:
>>
>> > Chris,
>> >
>> > The XSD model resolves imports on demand so if no name from the
>> imported
>> > namespace is referenced, the import will not be resolved. In that case
>> > the model produces a warning message (not an error message); this is
>> > very similar to the unused import warning you get for a in a .java file
>> > in Eclipse.
>> >
>> > For the particular example below, it would be just as well to generate
>> > directly from the schema; you an enter a URL directly into the import
>> > wizard...
>> >
>> >
>> > Chris Giblin wrote:
>> >
>> >> Whoops ---
>> >>
>> >> I spoke too soon - it looks like a problem, after all.
>> >> I am able to create a model using the imported schema.
>> >> However, when that same schema is imported by the wsdl file, the error
>> >> message, "location not resolved", occurs and a model is not produced.
>> >>
>> >> Any suggestions?
>> >>
>> >> Thanks, chris
>> >>
>> >> Chris Giblin wrote:
>> >> > Hello,
>> >> > I just realized that the imported schema itself imports a schema
>> >> > location which is not resolvable.
>> >> >
>> >> > Consider this problem closed!
>> >> >
>> >> > Thaks, chris
>> >> >
>> >> >
>> >> >
>> >> > Chris Giblin wrote:
>> >> >
>> >> >> Hello,
>> >> >>
>> >> >> I am trying to produce a genmodel from wsdl using the latest
>> emf/xsd
>> >> >> release and am receiving an unexpected error.
>> >> >>
>> >> >> I try to create a model using :
>> >> >> New > EMF Models > Load from XML Schema
>> >> >>
>> >> >> Specifying my wsdl file as input, I receive the following error:
>> >> >>
>> >> >> Problems were detected while validating and converting the XML
>> Schemas
>> >> >> Warning: XSD: The location 'http://schemas.xmlsoap.org/abc'
>> has not
>> >> >> been resolved : URI platform:/resource/myproject/xsd/abc.wsdl
>> Line 46
>> >> >> Column 10
>> >> >>
>> >> >> The offending statement is the xs:import shown below with URI's
>> >> >> obfuscated:
>> >> >>
>> >> >> <wsdl:types>
>> >> >> <xs:schema>
>> >> >> <xs:import namespace="http://schemas.xmlsoap.org/abc"
>> >> >> schemaLocation="http://schemas.xmlsoap.org/abc"/
>> <http://schemas.xmlsoap.org/abc>
>> >> <http://schemas.xmlsoap.org/abc>>
>> >> >> </xs:schema>
>> >> >> </wsdl:types>
>> >> >>
>> >> >> With a web browser, I am indeed able to retrieve the troublesome
>> >> >> schema, so I am sure the spec is OK. When then the error message,
>> >> >> "location .. has not been resolved"?
>> >> >>
>> >> >> The eclipse log contains no related entries.
>> >> >> Eclipse is started with :
>> >> >> -Djava.endorsed.dirs=plugins/org.apache.xerces_4.0.13
>> >> >>
>> >> >> My versions:
>> >> >> java.fullversion=J2RE 1.4.0 IBM Windows 32 build cn140-20020902
>> >> >> Eclipse: 3.0.0 Build id: 200401281649
>> >> >> EMF 2.0 20040127_1738SL
>> >> >> XSD 2.0 20040127_1738SL
>> >> >>
>> >> >>
>> >> >> What am I overlooking?
>> >> >>
>> >> >> Thanks, chris
>> >> >>
>> >>
>>
|
|
|
Goto Forum:
Current Time: Wed Apr 24 21:25:05 GMT 2024
Powered by FUDForum. Page generated in 0.04051 seconds |
] 
Search
Help
Register
Login
Home
