Eclipse Community Forums: XML Schema Definition (XSD)

Help

Home

Home » Archived » XML Schema Definition (XSD) » SchemaLocation help

Show: Today's Messages :: Show Polls :: Message Navigator

SchemaLocation help [message #43456]

Tue, 04 May 2004 21:23

Lance Phillips

Messages: 210
Registered: July 2009

Senior Member

In our XSDImport objects, we are setting the namespace attribute with no
problems. However, our schemaLocation values don't seem to be working. I'm
using the relative file path to the importing schema. What SHOULD I be
using there. Per the spec, it appears that it may be valid to just use the
namespace attribute in BOTH fields??? With the value set to relative file
paths, I get a warning after validation stating that the location could not
be resolved.

thanks,

lp

Report message to a moderator

Re: SchemaLocation help [message #43490 is a reply to message #43456]

Tue, 04 May 2004 21:32

Eclipse User

Originally posted by: merks.ca.ibm.com

Lance,

What's the URI of the document containing the reference? It must be absolute
for relative references to resolve.

Lance Phillips wrote:

> In our XSDImport objects, we are setting the namespace attribute with no
> problems. However, our schemaLocation values don't seem to be working. I'm
> using the relative file path to the importing schema. What SHOULD I be
> using there. Per the spec, it appears that it may be valid to just use the
> namespace attribute in BOTH fields??? With the value set to relative file
> paths, I get a warning after validation stating that the location could not
> be resolved.
>
> thanks,
>
> lp

Report message to a moderator

Re: SchemaLocation help [message #43553 is a reply to message #43490]

Wed, 05 May 2004 12:18

Lance Phillips

Messages: 210
Registered: July 2009

Senior Member

Ed,
I converted the schema location to an absolute path and now I'm getting
the following:
XSD: The value
'e:\Plugins\current\runtime-workspace\testing\soap_encoding. xsd' of
attribute 'schemaLocation' must be of type
'http://www.w3.org/2001/XMLSchema#anyURI'

thanks,

lp

"Ed Merks" <merks@ca.ibm.com> wrote in message
news:40980BE6.7E6DEFD4@ca.ibm.com...
> Lance,
>
> What's the URI of the document containing the reference? It must be
absolute
> for relative references to resolve.
>
>
> Lance Phillips wrote:
>
> > In our XSDImport objects, we are setting the namespace attribute with no
> > problems. However, our schemaLocation values don't seem to be working.
I'm
> > using the relative file path to the importing schema. What SHOULD I be
> > using there. Per the spec, it appears that it may be valid to just use
the
> > namespace attribute in BOTH fields??? With the value set to relative
file
> > paths, I get a warning after validation stating that the location could
not
> > be resolved.
> >
> > thanks,
> >
> > lp
>

Report message to a moderator

Re: SchemaLocation help [message #43583 is a reply to message #43553]

Wed, 05 May 2004 12:40

Eclipse User

Originally posted by: merks.ca.ibm.com

Lance,

I was recommending that the URI of the containing document/Resource should be
absolute not changing the schema location to be absolute; it's better to use
relative schema locations as much as possible. A URI uses "/" not "\"; a file
system path is not a URI.

Lance Phillips wrote:

> Ed,
> I converted the schema location to an absolute path and now I'm getting
> the following:
> XSD: The value
> 'e:\Plugins\current\runtime-workspace\testing\soap_encoding. xsd' of
> attribute 'schemaLocation' must be of type
> 'http://www.w3.org/2001/XMLSchema#anyURI'
>
> thanks,
>
> lp
>
> "Ed Merks" <merks@ca.ibm.com> wrote in message
> news:40980BE6.7E6DEFD4@ca.ibm.com...
> > Lance,
> >
> > What's the URI of the document containing the reference? It must be
> absolute
> > for relative references to resolve.
> >
> >
> > Lance Phillips wrote:
> >
> > > In our XSDImport objects, we are setting the namespace attribute with no
> > > problems. However, our schemaLocation values don't seem to be working.
> I'm
> > > using the relative file path to the importing schema. What SHOULD I be
> > > using there. Per the spec, it appears that it may be valid to just use
> the
> > > namespace attribute in BOTH fields??? With the value set to relative
> file
> > > paths, I get a warning after validation stating that the location could
> not
> > > be resolved.
> > >
> > > thanks,
> > >
> > > lp
> >

Report message to a moderator

Re: SchemaLocation help [message #43614 is a reply to message #43583]

Wed, 05 May 2004 13:34

Lance Phillips

Messages: 210
Registered: July 2009

Senior Member

Hmmmm.... I seem to have all kinds of issues with references. None of my
cross schema references resolve. I get an error for everything that refers
to something in another schema. The NS is correct in both Schemas. The
error looks like this:
XSD: Attribute group reference
' http://namespace.worldnet.ml.com/EDSI/Party/Datatypes/PartyD atatypes_v5_2#a
rrayAttributes' is unresolved

The PartyDatatypes schema exists and has been read into a resource in the
same resourceSet as the referencing schema. I've stepped through it in
debug and the references all get correctly set to the correct EObject from
the other schema... but when I validate I get the above exception.

Any ideas? My import looks like this (both files exist in the same
directory)....
<xs:import
namespace= http://namespace.worldnet.ml.com/EDSI/Standards/Datatypes/St andard
Datatypes_1_1 schemaLocation="StandardDatatypes_1_1.xsd" />

thanks,

lp

"Ed Merks" <merks@ca.ibm.com> wrote in message
news:4098E0CA.B3309D0A@ca.ibm.com...
> Lance,
>
> I was recommending that the URI of the containing document/Resource should
be
> absolute not changing the schema location to be absolute; it's better to
use
> relative schema locations as much as possible. A URI uses "/" not "\"; a
file
> system path is not a URI.
>
>
> Lance Phillips wrote:
>
> > Ed,
> > I converted the schema location to an absolute path and now I'm
getting
> > the following:
> > XSD: The value
> > 'e:\Plugins\current\runtime-workspace\testing\soap_encoding. xsd' of
> > attribute 'schemaLocation' must be of type
> > 'http://www.w3.org/2001/XMLSchema#anyURI'
> >
> > thanks,
> >
> > lp
> >
> > "Ed Merks" <merks@ca.ibm.com> wrote in message
> > news:40980BE6.7E6DEFD4@ca.ibm.com...
> > > Lance,
> > >
> > > What's the URI of the document containing the reference? It must be
> > absolute
> > > for relative references to resolve.
> > >
> > >
> > > Lance Phillips wrote:
> > >
> > > > In our XSDImport objects, we are setting the namespace attribute wit
h no
> > > > problems. However, our schemaLocation values don't seem to be
working.
> > I'm
> > > > using the relative file path to the importing schema. What SHOULD I
be
> > > > using there. Per the spec, it appears that it may be valid to just
use
> > the
> > > > namespace attribute in BOTH fields??? With the value set to
relative
> > file
> > > > paths, I get a warning after validation stating that the location
could
> > not
> > > > be resolved.
> > > >
> > > > thanks,
> > > >
> > > > lp
> > >
>

Report message to a moderator

Re: SchemaLocation help [message #43677 is a reply to message #43614]

Wed, 05 May 2004 18:30

Eclipse User

Originally posted by: merks.ca.ibm.com

Lance,

What is the URI of the document/Resource containing these?

Lance Phillips wrote:

> Hmmmm.... I seem to have all kinds of issues with references. None of my
> cross schema references resolve. I get an error for everything that refers
> to something in another schema. The NS is correct in both Schemas. The
> error looks like this:
> XSD: Attribute group reference
> ' http://namespace.worldnet.ml.com/EDSI/Party/Datatypes/PartyD atatypes_v5_2#a
> rrayAttributes' is unresolved
>
> The PartyDatatypes schema exists and has been read into a resource in the
> same resourceSet as the referencing schema. I've stepped through it in
> debug and the references all get correctly set to the correct EObject from
> the other schema... but when I validate I get the above exception.
>
> Any ideas? My import looks like this (both files exist in the same
> directory)....
> <xs:import
> namespace= http://namespace.worldnet.ml.com/EDSI/Standards/Datatypes/St andard
> Datatypes_1_1 schemaLocation="StandardDatatypes_1_1.xsd" />
>
> thanks,
>
> lp
>
> "Ed Merks" <merks@ca.ibm.com> wrote in message
> news:4098E0CA.B3309D0A@ca.ibm.com...
> > Lance,
> >
> > I was recommending that the URI of the containing document/Resource should
> be
> > absolute not changing the schema location to be absolute; it's better to
> use
> > relative schema locations as much as possible. A URI uses "/" not "\"; a
> file
> > system path is not a URI.
> >
> >
> > Lance Phillips wrote:
> >
> > > Ed,
> > > I converted the schema location to an absolute path and now I'm
> getting
> > > the following:
> > > XSD: The value
> > > 'e:\Plugins\current\runtime-workspace\testing\soap_encoding. xsd' of
> > > attribute 'schemaLocation' must be of type
> > > 'http://www.w3.org/2001/XMLSchema#anyURI'
> > >
> > > thanks,
> > >
> > > lp
> > >
> > > "Ed Merks" <merks@ca.ibm.com> wrote in message
> > > news:40980BE6.7E6DEFD4@ca.ibm.com...
> > > > Lance,
> > > >
> > > > What's the URI of the document containing the reference? It must be
> > > absolute
> > > > for relative references to resolve.
> > > >
> > > >
> > > > Lance Phillips wrote:
> > > >
> > > > > In our XSDImport objects, we are setting the namespace attribute wit
> h no
> > > > > problems. However, our schemaLocation values don't seem to be
> working.
> > > I'm
> > > > > using the relative file path to the importing schema. What SHOULD I
> be
> > > > > using there. Per the spec, it appears that it may be valid to just
> use
> > > the
> > > > > namespace attribute in BOTH fields??? With the value set to
> relative
> > > file
> > > > > paths, I get a warning after validation stating that the location
> could
> > > not
> > > > > be resolved.
> > > > >
> > > > > thanks,
> > > > >
> > > > > lp
> > > >
> >

Report message to a moderator

Re: SchemaLocation help [message #43739 is a reply to message #43677]

Wed, 05 May 2004 20:15

Lance Phillips

Messages: 210
Registered: July 2009

Senior Member

The uris for the resources are :
file:/e:/Plugins/current/runtime-workspace/testing/Organizat ion_v5_2.xsd
file:/e:/Plugins/current/runtime-workspace/testing/PartyData types_v5_2.xsd

The targetNamespaces are :
The uri for the importing schema is
http://namespace.worldnet.ml.com/EDSI/Party/Organization_v5_ 2
The uri for the imported schema is
http://namespace.worldnet.ml.com/EDSI/Party/Datatypes/PartyD atatypes_v5_2

The crazy thing is that arrayAttributes that it can't find (per the message
below) is contained in
file:/e:/Plugins/current/runtime-workspace/testing/soap_enco ding.xsd which
is also imported by Organization.

thanks,

lp

"Ed Merks" <merks@ca.ibm.com> wrote in message
news:409932CD.5995F79C@ca.ibm.com...
> Lance,
>
> What is the URI of the document/Resource containing these?
>
>
> Lance Phillips wrote:
>
> > Hmmmm.... I seem to have all kinds of issues with references. None of
my
> > cross schema references resolve. I get an error for everything that
refers
> > to something in another schema. The NS is correct in both Schemas. The
> > error looks like this:
> > XSD: Attribute group reference
> >
' http://namespace.worldnet.ml.com/EDSI/Party/Datatypes/PartyD atatypes_v5_2#a
> > rrayAttributes' is unresolved
> >
> > The PartyDatatypes schema exists and has been read into a resource in
the
> > same resourceSet as the referencing schema. I've stepped through it in
> > debug and the references all get correctly set to the correct EObject
from
> > the other schema... but when I validate I get the above exception.
> >
> > Any ideas? My import looks like this (both files exist in the same
> > directory)....
> > <xs:import
> >
namespace= http://namespace.worldnet.ml.com/EDSI/Standards/Datatypes/St andard
> > Datatypes_1_1 schemaLocation="StandardDatatypes_1_1.xsd" />
> >
> > thanks,
> >
> > lp
> >
> > "Ed Merks" <merks@ca.ibm.com> wrote in message
> > news:4098E0CA.B3309D0A@ca.ibm.com...
> > > Lance,
> > >
> > > I was recommending that the URI of the containing document/Resource
should
> > be
> > > absolute not changing the schema location to be absolute; it's better
to
> > use
> > > relative schema locations as much as possible. A URI uses "/" not
"\"; a
> > file
> > > system path is not a URI.
> > >
> > >
> > > Lance Phillips wrote:
> > >
> > > > Ed,
> > > > I converted the schema location to an absolute path and now I'm
> > getting
> > > > the following:
> > > > XSD: The value
> > > > 'e:\Plugins\current\runtime-workspace\testing\soap_encoding. xsd' of
> > > > attribute 'schemaLocation' must be of type
> > > > 'http://www.w3.org/2001/XMLSchema#anyURI'
> > > >
> > > > thanks,
> > > >
> > > > lp
> > > >
> > > > "Ed Merks" <merks@ca.ibm.com> wrote in message
> > > > news:40980BE6.7E6DEFD4@ca.ibm.com...
> > > > > Lance,
> > > > >
> > > > > What's the URI of the document containing the reference? It must
be
> > > > absolute
> > > > > for relative references to resolve.
> > > > >
> > > > >
> > > > > Lance Phillips wrote:
> > > > >
> > > > > > In our XSDImport objects, we are setting the namespace attribute
wit
> > h no
> > > > > > problems. However, our schemaLocation values don't seem to be
> > working.
> > > > I'm
> > > > > > using the relative file path to the importing schema. What
SHOULD I
> > be
> > > > > > using there. Per the spec, it appears that it may be valid to
just
> > use
> > > > the
> > > > > > namespace attribute in BOTH fields??? With the value set to
> > relative
> > > > file
> > > > > > paths, I get a warning after validation stating that the
location
> > could
> > > > not
> > > > > > be resolved.
> > > > > >
> > > > > > thanks,
> > > > > >
> > > > > > lp
> > > > >
> > >
>

Report message to a moderator

Re: SchemaLocation help [message #586655 is a reply to message #43456]

Tue, 04 May 2004 21:32

Ed Merks

Messages: 33137
Registered: July 2009

Senior Member

Lance,

What's the URI of the document containing the reference? It must be absolute
for relative references to resolve.

Lance Phillips wrote:

> In our XSDImport objects, we are setting the namespace attribute with no
> problems. However, our schemaLocation values don't seem to be working. I'm
> using the relative file path to the importing schema. What SHOULD I be
> using there. Per the spec, it appears that it may be valid to just use the
> namespace attribute in BOTH fields??? With the value set to relative file
> paths, I get a warning after validation stating that the location could not
> be resolved.
>
> thanks,
>
> lp

Ed Merks
Professional Support: https://www.macromodeling.com/

Report message to a moderator

Re: SchemaLocation help [message #586677 is a reply to message #43490]

Wed, 05 May 2004 12:18

Lance Phillips

Messages: 210
Registered: July 2009

Senior Member

Report message to a moderator

Re: SchemaLocation help [message #586687 is a reply to message #43553]

Wed, 05 May 2004 12:40

Ed Merks

Messages: 33137
Registered: July 2009

Senior Member

Lance,

I was recommending that the URI of the containing document/Resource should be
absolute not changing the schema location to be absolute; it's better to use
relative schema locations as much as possible. A URI uses "/" not "\"; a file
system path is not a URI.

Lance Phillips wrote:

> Ed,
> I converted the schema location to an absolute path and now I'm getting
> the following:
> XSD: The value
> 'e:\Plugins\current\runtime-workspace\testing\soap_encoding. xsd' of
> attribute 'schemaLocation' must be of type
> 'http://www.w3.org/2001/XMLSchema#anyURI'
>
> thanks,
>
> lp
>
> "Ed Merks" <merks@ca.ibm.com> wrote in message
> news:40980BE6.7E6DEFD4@ca.ibm.com...
> > Lance,
> >
> > What's the URI of the document containing the reference? It must be
> absolute
> > for relative references to resolve.
> >
> >
> > Lance Phillips wrote:
> >
> > > In our XSDImport objects, we are setting the namespace attribute with no
> > > problems. However, our schemaLocation values don't seem to be working.
> I'm
> > > using the relative file path to the importing schema. What SHOULD I be
> > > using there. Per the spec, it appears that it may be valid to just use
> the
> > > namespace attribute in BOTH fields??? With the value set to relative
> file
> > > paths, I get a warning after validation stating that the location could
> not
> > > be resolved.
> > >
> > > thanks,
> > >
> > > lp
> >

Ed Merks
Professional Support: https://www.macromodeling.com/

Report message to a moderator

Re: SchemaLocation help [message #586695 is a reply to message #43583]

Wed, 05 May 2004 13:34

Lance Phillips

Messages: 210
Registered: July 2009

Senior Member

Report message to a moderator

Re: SchemaLocation help [message #586727 is a reply to message #43614]

Wed, 05 May 2004 18:30

Ed Merks

Messages: 33137
Registered: July 2009

Senior Member

Lance,

What is the URI of the document/Resource containing these?

Lance Phillips wrote:

> Hmmmm.... I seem to have all kinds of issues with references. None of my
> cross schema references resolve. I get an error for everything that refers
> to something in another schema. The NS is correct in both Schemas. The
> error looks like this:
> XSD: Attribute group reference
> ' http://namespace.worldnet.ml.com/EDSI/Party/Datatypes/PartyD atatypes_v5_2#a
> rrayAttributes' is unresolved
>
> The PartyDatatypes schema exists and has been read into a resource in the
> same resourceSet as the referencing schema. I've stepped through it in
> debug and the references all get correctly set to the correct EObject from
> the other schema... but when I validate I get the above exception.
>
> Any ideas? My import looks like this (both files exist in the same
> directory)....
> <xs:import
> namespace= http://namespace.worldnet.ml.com/EDSI/Standards/Datatypes/St andard
> Datatypes_1_1 schemaLocation="StandardDatatypes_1_1.xsd" />
>
> thanks,
>
> lp
>
> "Ed Merks" <merks@ca.ibm.com> wrote in message
> news:4098E0CA.B3309D0A@ca.ibm.com...
> > Lance,
> >
> > I was recommending that the URI of the containing document/Resource should
> be
> > absolute not changing the schema location to be absolute; it's better to
> use
> > relative schema locations as much as possible. A URI uses "/" not "\"; a
> file
> > system path is not a URI.
> >
> >
> > Lance Phillips wrote:
> >
> > > Ed,
> > > I converted the schema location to an absolute path and now I'm
> getting
> > > the following:
> > > XSD: The value
> > > 'e:\Plugins\current\runtime-workspace\testing\soap_encoding. xsd' of
> > > attribute 'schemaLocation' must be of type
> > > 'http://www.w3.org/2001/XMLSchema#anyURI'
> > >
> > > thanks,
> > >
> > > lp
> > >
> > > "Ed Merks" <merks@ca.ibm.com> wrote in message
> > > news:40980BE6.7E6DEFD4@ca.ibm.com...
> > > > Lance,
> > > >
> > > > What's the URI of the document containing the reference? It must be
> > > absolute
> > > > for relative references to resolve.
> > > >
> > > >
> > > > Lance Phillips wrote:
> > > >
> > > > > In our XSDImport objects, we are setting the namespace attribute wit
> h no
> > > > > problems. However, our schemaLocation values don't seem to be
> working.
> > > I'm
> > > > > using the relative file path to the importing schema. What SHOULD I
> be
> > > > > using there. Per the spec, it appears that it may be valid to just
> use
> > > the
> > > > > namespace attribute in BOTH fields??? With the value set to
> relative
> > > file
> > > > > paths, I get a warning after validation stating that the location
> could
> > > not
> > > > > be resolved.
> > > > >
> > > > > thanks,
> > > > >
> > > > > lp
> > > >
> >

Ed Merks
Professional Support: https://www.macromodeling.com/

Report message to a moderator