Home » Archived » XML Schema Definition (XSD) » Schema Validation Problem
| Schema Validation Problem [message #39105] |
Sat, 20 March 2004 00:08  |
Eclipse User |
|
|
|
Originally posted by: cipher8000.yahoo.com
I am using 20040127_1738SL build. I have two schemas 1.boo.xsd 2. foo.xsd.
boo.xsd imports "foo" schema. foo.xsd is invalid because i used
type="xsd:aaaa". When i validate boo.xsd, the validate() doesn't populate
any diagnostic error messages. But if i validate foo.xsd seperately, i get
diagnostic error messages for unresolved type "xsd:aaaa"
this combination used to work in previous build.
here is the boo.xsd:
<schema attributeFormDefault="qualified" elementFormDefault="qualified"
targetNamespace="http://schemas.xmlsoap.org/wsdl/"
xmlns="http://www.w3.org/2001/XMLSchema" xmlns:foo="http://foo.com">
<import namespace="http://foo.com" schemaLocation="foo.xsd"/>
<element name="fooElement" type="foo:fooElementType"/>
</schema>
here is the foo.xsd
<xsd:schema targetNamespace="http://foo.com"
xmlns="http://foo.com"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified">
<xsd:complexType name="fooElementType">
<xsd:sequence>
<xsd:element name="end" type="xsd:aaaa"/>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
thanks
-muruga
|
|
|
| Re: Schema Validation Problem [message #39136 is a reply to message #39105] |
Sat, 20 March 2004 00:28  |
| Eclipse User |
|
|
|
Originally posted by: cipher8000.yahoo.com
I tried the latest build Build I20040308163 also. It behaves same.
thanks
-muruga
"Muruga Chinnananchi" <cipher8000@yahoo.com> wrote in message
news:c3g1oj$5i6$1@eclipse.org...
> I am using 20040127_1738SL build. I have two schemas 1.boo.xsd 2. foo.xsd.
>
> boo.xsd imports "foo" schema. foo.xsd is invalid because i used
> type="xsd:aaaa". When i validate boo.xsd, the validate() doesn't populate
> any diagnostic error messages. But if i validate foo.xsd seperately, i get
> diagnostic error messages for unresolved type "xsd:aaaa"
>
> this combination used to work in previous build.
>
> here is the boo.xsd:
> <schema attributeFormDefault="qualified" elementFormDefault="qualified"
> targetNamespace="http://schemas.xmlsoap.org/wsdl/"
> xmlns="http://www.w3.org/2001/XMLSchema" xmlns:foo="http://foo.com">
> <import namespace="http://foo.com" schemaLocation="foo.xsd"/>
> <element name="fooElement" type="foo:fooElementType"/>
> </schema>
>
> here is the foo.xsd
> <xsd:schema targetNamespace="http://foo.com"
> xmlns="http://foo.com"
> xmlns:xsd="http://www.w3.org/2001/XMLSchema"
> elementFormDefault="qualified">
> <xsd:complexType name="fooElementType">
> <xsd:sequence>
> <xsd:element name="end" type="xsd:aaaa"/>
> </xsd:sequence>
> </xsd:complexType>
> </xsd:schema>
>
> thanks
> -muruga
>
>
|
|
|
| Re: Schema Validation Problem [message #39167 is a reply to message #39105] |
Mon, 22 March 2004 11:43 |
| Eclipse User |
|
|
|
Originally posted by: merks.ca.ibm.com
Muruga,
You have to collect diagnostics from each schema resource; it's always worked
this way. Have a look at how the XSDMainTest supports -validate by walking
each resource.
Muruga Chinnananchi wrote:
> I am using 20040127_1738SL build. I have two schemas 1.boo.xsd 2. foo.xsd.
>
> boo.xsd imports "foo" schema. foo.xsd is invalid because i used
> type="xsd:aaaa". When i validate boo.xsd, the validate() doesn't populate
> any diagnostic error messages. But if i validate foo.xsd seperately, i get
> diagnostic error messages for unresolved type "xsd:aaaa"
>
> this combination used to work in previous build.
>
> here is the boo.xsd:
> <schema attributeFormDefault="qualified" elementFormDefault="qualified"
> targetNamespace="http://schemas.xmlsoap.org/wsdl/"
> xmlns="http://www.w3.org/2001/XMLSchema" xmlns:foo="http://foo.com">
> <import namespace="http://foo.com" schemaLocation="foo.xsd"/>
> <element name="fooElement" type="foo:fooElementType"/>
> </schema>
>
> here is the foo.xsd
> <xsd:schema targetNamespace="http://foo.com"
> xmlns="http://foo.com"
> xmlns:xsd="http://www.w3.org/2001/XMLSchema"
> elementFormDefault="qualified">
> <xsd:complexType name="fooElementType">
> <xsd:sequence>
> <xsd:element name="end" type="xsd:aaaa"/>
> </xsd:sequence>
> </xsd:complexType>
> </xsd:schema>
>
> thanks
> -muruga
|
|
|
| Re: Schema Validation Problem [message #39198 is a reply to message #39167] |
Tue, 23 March 2004 00:07 |
| Eclipse User |
|
|
|
Originally posted by: cipher8000.yahoo.com
Hi Ed,
Thanks very much. It works now. I traverse all the imports and try to
validate them seperately.
I have another problem. I have a schema eoli.xsd, XMLSpy validates with no
error. But eclipse xsd throws these error when i tried to validate. I am
attaching this schema (eoli.xsd). Looks like this is valid schema.
Error at line 374, in
"file:////c:/customer/spacebel/HelloWorld/services/eoli.xsd". XSD: The type
of element 'http://earth.esa.int/XML/eoli#geoEle' must derive from
'http://earth.esa.int/XML/eoli#geoEle_._type'
Error at line 401, in
"file:////c:/customer/spacebel/HelloWorld/services/eoli.xsd". XSD: The type
of element 'http://earth.esa.int/XML/eoli#tempEle' must derive from
'http://earth.esa.int/XML/eoli#EX_TemporalExtendType'
Error at line 370, in
"file:////c:/customer/spacebel/HelloWorld/services/eoli.xsd". XSD: The
restricted content type must accept a subset of the content accepted by the
base type
Error at line 791, in
"file:////c:/customer/spacebel/HelloWorld/services/eoli.xsd". XSD: The
restricted content type must accept a subset of the content accepted by the
base type
thanks,
-muruga
"Ed Merks" <merks@ca.ibm.com> wrote in message
news:405ED169.43E4B2DB@ca.ibm.com...
> Muruga,
>
> You have to collect diagnostics from each schema resource; it's always
worked
> this way. Have a look at how the XSDMainTest supports -validate by
walking
> each resource.
>
>
> Muruga Chinnananchi wrote:
>
> > I am using 20040127_1738SL build. I have two schemas 1.boo.xsd 2.
foo.xsd.
> >
> > boo.xsd imports "foo" schema. foo.xsd is invalid because i used
> > type="xsd:aaaa". When i validate boo.xsd, the validate() doesn't
populate
> > any diagnostic error messages. But if i validate foo.xsd seperately, i
get
> > diagnostic error messages for unresolved type "xsd:aaaa"
> >
> > this combination used to work in previous build.
> >
> > here is the boo.xsd:
> > <schema attributeFormDefault="qualified" elementFormDefault="qualified"
> > targetNamespace="http://schemas.xmlsoap.org/wsdl/"
> > xmlns="http://www.w3.org/2001/XMLSchema" xmlns:foo="http://foo.com">
> > <import namespace="http://foo.com" schemaLocation="foo.xsd"/>
> > <element name="fooElement" type="foo:fooElementType"/>
> > </schema>
> >
> > here is the foo.xsd
> > <xsd:schema targetNamespace="http://foo.com"
> > xmlns="http://foo.com"
> > xmlns:xsd="http://www.w3.org/2001/XMLSchema"
> > elementFormDefault="qualified">
> > <xsd:complexType name="fooElementType">
> > <xsd:sequence>
> > <xsd:element name="end" type="xsd:aaaa"/>
> > </xsd:sequence>
> > </xsd:complexType>
> > </xsd:schema>
> >
> > thanks
> > -muruga
>
|
|
|
| Re: Schema Validation Problem [message #39228 is a reply to message #39198] |
Tue, 23 March 2004 00:09 |
| Eclipse User |
|
|
|
Originally posted by: cipher8000.yahoo.com
oops i forgot to attach that schema file.
thanks
-muruga
"Muruga Chinnananchi" <cipher8000@yahoo.com> wrote in message
news:c3nurp$r8$1@eclipse.org...
> Hi Ed,
>
> Thanks very much. It works now. I traverse all the imports and try to
> validate them seperately.
>
> I have another problem. I have a schema eoli.xsd, XMLSpy validates with no
> error. But eclipse xsd throws these error when i tried to validate. I am
> attaching this schema (eoli.xsd). Looks like this is valid schema.
>
> Error at line 374, in
> "file:////c:/customer/spacebel/HelloWorld/services/eoli.xsd". XSD: The
type
> of element 'http://earth.esa.int/XML/eoli#geoEle' must derive from
> 'http://earth.esa.int/XML/eoli#geoEle_._type'
> Error at line 401, in
> "file:////c:/customer/spacebel/HelloWorld/services/eoli.xsd". XSD: The
type
> of element 'http://earth.esa.int/XML/eoli#tempEle' must derive from
> 'http://earth.esa.int/XML/eoli#EX_TemporalExtendType'
> Error at line 370, in
> "file:////c:/customer/spacebel/HelloWorld/services/eoli.xsd". XSD: The
> restricted content type must accept a subset of the content accepted by
the
> base type
> Error at line 791, in
> "file:////c:/customer/spacebel/HelloWorld/services/eoli.xsd". XSD: The
> restricted content type must accept a subset of the content accepted by
the
> base type
>
> thanks,
> -muruga
>
>
> "Ed Merks" <merks@ca.ibm.com> wrote in message
> news:405ED169.43E4B2DB@ca.ibm.com...
> > Muruga,
> >
> > You have to collect diagnostics from each schema resource; it's always
> worked
> > this way. Have a look at how the XSDMainTest supports -validate by
> walking
> > each resource.
> >
> >
> > Muruga Chinnananchi wrote:
> >
> > > I am using 20040127_1738SL build. I have two schemas 1.boo.xsd 2.
> foo.xsd.
> > >
> > > boo.xsd imports "foo" schema. foo.xsd is invalid because i used
> > > type="xsd:aaaa". When i validate boo.xsd, the validate() doesn't
> populate
> > > any diagnostic error messages. But if i validate foo.xsd seperately, i
> get
> > > diagnostic error messages for unresolved type "xsd:aaaa"
> > >
> > > this combination used to work in previous build.
> > >
> > > here is the boo.xsd:
> > > <schema attributeFormDefault="qualified"
elementFormDefault="qualified"
> > > targetNamespace="http://schemas.xmlsoap.org/wsdl/"
> > > xmlns="http://www.w3.org/2001/XMLSchema"
xmlns:foo="http://foo.com">
> > > <import namespace="http://foo.com" schemaLocation="foo.xsd"/>
> > > <element name="fooElement" type="foo:fooElementType"/>
> > > </schema>
> > >
> > > here is the foo.xsd
> > > <xsd:schema targetNamespace="http://foo.com"
> > > xmlns="http://foo.com"
> > > xmlns:xsd="http://www.w3.org/2001/XMLSchema"
> > > elementFormDefault="qualified">
> > > <xsd:complexType name="fooElementType">
> > > <xsd:sequence>
> > > <xsd:element name="end" type="xsd:aaaa"/>
> > > </xsd:sequence>
> > > </xsd:complexType>
> > > </xsd:schema>
> > >
> > > thanks
> > > -muruga
> >
>
>
Attachment: eoli.xsd
(Size: 46.23KB, Downloaded 344 times)
|
|
|
| Re: Schema Validation Problem [message #39259 is a reply to message #39228] |
Tue, 23 March 2004 11:11 |
| Eclipse User |
|
|
|
Originally posted by: merks.ca.ibm.com
Muruga,
These all appear to be legitimate errors that XMLSpy overlooked.
Muruga Chinnananchi wrote:
> oops i forgot to attach that schema file.
>
> thanks
> -muruga
>
> "Muruga Chinnananchi" <cipher8000@yahoo.com> wrote in message
> news:c3nurp$r8$1@eclipse.org...
> > Hi Ed,
> >
> > Thanks very much. It works now. I traverse all the imports and try to
> > validate them seperately.
> >
> > I have another problem. I have a schema eoli.xsd, XMLSpy validates with no
> > error. But eclipse xsd throws these error when i tried to validate. I am
> > attaching this schema (eoli.xsd). Looks like this is valid schema.
> >
> > Error at line 374, in
> > "file:////c:/customer/spacebel/HelloWorld/services/eoli.xsd". XSD: The
> type
> > of element 'http://earth.esa.int/XML/eoli#geoEle' must derive from
> > 'http://earth.esa.int/XML/eoli#geoEle_._type'
> > Error at line 401, in
> > "file:////c:/customer/spacebel/HelloWorld/services/eoli.xsd". XSD: The
> type
> > of element 'http://earth.esa.int/XML/eoli#tempEle' must derive from
> > 'http://earth.esa.int/XML/eoli#EX_TemporalExtendType'
> > Error at line 370, in
> > "file:////c:/customer/spacebel/HelloWorld/services/eoli.xsd". XSD: The
> > restricted content type must accept a subset of the content accepted by
> the
> > base type
> > Error at line 791, in
> > "file:////c:/customer/spacebel/HelloWorld/services/eoli.xsd". XSD: The
> > restricted content type must accept a subset of the content accepted by
> the
> > base type
> >
> > thanks,
> > -muruga
> >
> >
> > "Ed Merks" <merks@ca.ibm.com> wrote in message
> > news:405ED169.43E4B2DB@ca.ibm.com...
> > > Muruga,
> > >
> > > You have to collect diagnostics from each schema resource; it's always
> > worked
> > > this way. Have a look at how the XSDMainTest supports -validate by
> > walking
> > > each resource.
> > >
> > >
> > > Muruga Chinnananchi wrote:
> > >
> > > > I am using 20040127_1738SL build. I have two schemas 1.boo.xsd 2.
> > foo.xsd.
> > > >
> > > > boo.xsd imports "foo" schema. foo.xsd is invalid because i used
> > > > type="xsd:aaaa". When i validate boo.xsd, the validate() doesn't
> > populate
> > > > any diagnostic error messages. But if i validate foo.xsd seperately, i
>
> > get
> > > > diagnostic error messages for unresolved type "xsd:aaaa"
> > > >
> > > > this combination used to work in previous build.
> > > >
> > > > here is the boo.xsd:
> > > > <schema attributeFormDefault="qualified"
> elementFormDefault="qualified"
> > > > targetNamespace="http://schemas.xmlsoap.org/wsdl/"
> > > > xmlns="http://www.w3.org/2001/XMLSchema"
> xmlns:foo="http://foo.com">
> > > > <import namespace="http://foo.com" schemaLocation="foo.xsd"/>
> > > > <element name="fooElement" type="foo:fooElementType"/>
> > > > </schema>
> > > >
> > > > here is the foo.xsd
> > > > <xsd:schema targetNamespace="http://foo.com"
> > > > xmlns="http://foo.com"
> > > > xmlns:xsd="http://www.w3.org/2001/XMLSchema"
> > > > elementFormDefault="qualified">
> > > > <xsd:complexType name="fooElementType">
> > > > <xsd:sequence>
> > > > <xsd:element name="end" type="xsd:aaaa"/>
> > > > </xsd:sequence>
> > > > </xsd:complexType>
> > > > </xsd:schema>
> > > >
> > > > thanks
> > > > -muruga
> > >
> >
> >
>
> Name: eoli.xsd
> eoli.xsd Type: unspecified type (application/octet-stream)
> Encoding: x-uuencode
|
|
|
| Re: Schema Validation Problem [message #584332 is a reply to message #39105] |
Sat, 20 March 2004 00:28 |
| Eclipse User |
|
|
|
Originally posted by: cipher8000.yahoo.com
I tried the latest build Build I20040308163 also. It behaves same.
thanks
-muruga
"Muruga Chinnananchi" <cipher8000@yahoo.com> wrote in message
news:c3g1oj$5i6$1@eclipse.org...
> I am using 20040127_1738SL build. I have two schemas 1.boo.xsd 2. foo.xsd.
>
> boo.xsd imports "foo" schema. foo.xsd is invalid because i used
> type="xsd:aaaa". When i validate boo.xsd, the validate() doesn't populate
> any diagnostic error messages. But if i validate foo.xsd seperately, i get
> diagnostic error messages for unresolved type "xsd:aaaa"
>
> this combination used to work in previous build.
>
> here is the boo.xsd:
> <schema attributeFormDefault="qualified" elementFormDefault="qualified"
> targetNamespace="http://schemas.xmlsoap.org/wsdl/"
> xmlns="http://www.w3.org/2001/XMLSchema" xmlns:foo="http://foo.com">
> <import namespace="http://foo.com" schemaLocation="foo.xsd"/>
> <element name="fooElement" type="foo:fooElementType"/>
> </schema>
>
> here is the foo.xsd
> <xsd:schema targetNamespace="http://foo.com"
> xmlns="http://foo.com"
> xmlns:xsd="http://www.w3.org/2001/XMLSchema"
> elementFormDefault="qualified">
> <xsd:complexType name="fooElementType">
> <xsd:sequence>
> <xsd:element name="end" type="xsd:aaaa"/>
> </xsd:sequence>
> </xsd:complexType>
> </xsd:schema>
>
> thanks
> -muruga
>
>
|
|
|
| Re: Schema Validation Problem [message #584348 is a reply to message #39105] |
Mon, 22 March 2004 11:43 |
 Ed Merks
Messages: 33140
Registered: July 2009 |
Senior Member |
|
|
Muruga,
You have to collect diagnostics from each schema resource; it's always worked
this way. Have a look at how the XSDMainTest supports -validate by walking
each resource.
Muruga Chinnananchi wrote:
> I am using 20040127_1738SL build. I have two schemas 1.boo.xsd 2. foo.xsd.
>
> boo.xsd imports "foo" schema. foo.xsd is invalid because i used
> type="xsd:aaaa". When i validate boo.xsd, the validate() doesn't populate
> any diagnostic error messages. But if i validate foo.xsd seperately, i get
> diagnostic error messages for unresolved type "xsd:aaaa"
>
> this combination used to work in previous build.
>
> here is the boo.xsd:
> <schema attributeFormDefault="qualified" elementFormDefault="qualified"
> targetNamespace="http://schemas.xmlsoap.org/wsdl/"
> xmlns="http://www.w3.org/2001/XMLSchema" xmlns:foo="http://foo.com">
> <import namespace="http://foo.com" schemaLocation="foo.xsd"/>
> <element name="fooElement" type="foo:fooElementType"/>
> </schema>
>
> here is the foo.xsd
> <xsd:schema targetNamespace="http://foo.com"
> xmlns="http://foo.com"
> xmlns:xsd="http://www.w3.org/2001/XMLSchema"
> elementFormDefault="qualified">
> <xsd:complexType name="fooElementType">
> <xsd:sequence>
> <xsd:element name="end" type="xsd:aaaa"/>
> </xsd:sequence>
> </xsd:complexType>
> </xsd:schema>
>
> thanks
> -muruga
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
| Re: Schema Validation Problem [message #584366 is a reply to message #39167] |
Tue, 23 March 2004 00:07 |
| Eclipse User |
|
|
|
Originally posted by: cipher8000.yahoo.com
Hi Ed,
Thanks very much. It works now. I traverse all the imports and try to
validate them seperately.
I have another problem. I have a schema eoli.xsd, XMLSpy validates with no
error. But eclipse xsd throws these error when i tried to validate. I am
attaching this schema (eoli.xsd). Looks like this is valid schema.
Error at line 374, in
"file:////c:/customer/spacebel/HelloWorld/services/eoli.xsd". XSD: The type
of element 'http://earth.esa.int/XML/eoli#geoEle' must derive from
'http://earth.esa.int/XML/eoli#geoEle_._type'
Error at line 401, in
"file:////c:/customer/spacebel/HelloWorld/services/eoli.xsd". XSD: The type
of element 'http://earth.esa.int/XML/eoli#tempEle' must derive from
'http://earth.esa.int/XML/eoli#EX_TemporalExtendType'
Error at line 370, in
"file:////c:/customer/spacebel/HelloWorld/services/eoli.xsd". XSD: The
restricted content type must accept a subset of the content accepted by the
base type
Error at line 791, in
"file:////c:/customer/spacebel/HelloWorld/services/eoli.xsd". XSD: The
restricted content type must accept a subset of the content accepted by the
base type
thanks,
-muruga
"Ed Merks" <merks@ca.ibm.com> wrote in message
news:405ED169.43E4B2DB@ca.ibm.com...
> Muruga,
>
> You have to collect diagnostics from each schema resource; it's always
worked
> this way. Have a look at how the XSDMainTest supports -validate by
walking
> each resource.
>
>
> Muruga Chinnananchi wrote:
>
> > I am using 20040127_1738SL build. I have two schemas 1.boo.xsd 2.
foo.xsd.
> >
> > boo.xsd imports "foo" schema. foo.xsd is invalid because i used
> > type="xsd:aaaa". When i validate boo.xsd, the validate() doesn't
populate
> > any diagnostic error messages. But if i validate foo.xsd seperately, i
get
> > diagnostic error messages for unresolved type "xsd:aaaa"
> >
> > this combination used to work in previous build.
> >
> > here is the boo.xsd:
> > <schema attributeFormDefault="qualified" elementFormDefault="qualified"
> > targetNamespace="http://schemas.xmlsoap.org/wsdl/"
> > xmlns="http://www.w3.org/2001/XMLSchema" xmlns:foo="http://foo.com">
> > <import namespace="http://foo.com" schemaLocation="foo.xsd"/>
> > <element name="fooElement" type="foo:fooElementType"/>
> > </schema>
> >
> > here is the foo.xsd
> > <xsd:schema targetNamespace="http://foo.com"
> > xmlns="http://foo.com"
> > xmlns:xsd="http://www.w3.org/2001/XMLSchema"
> > elementFormDefault="qualified">
> > <xsd:complexType name="fooElementType">
> > <xsd:sequence>
> > <xsd:element name="end" type="xsd:aaaa"/>
> > </xsd:sequence>
> > </xsd:complexType>
> > </xsd:schema>
> >
> > thanks
> > -muruga
>
|
|
|
| Re: Schema Validation Problem [message #584377 is a reply to message #39198] |
Tue, 23 March 2004 00:09 |
| Eclipse User |
|
|
|
Originally posted by: cipher8000.yahoo.com
oops i forgot to attach that schema file.
thanks
-muruga
"Muruga Chinnananchi" <cipher8000@yahoo.com> wrote in message
news:c3nurp$r8$1@eclipse.org...
> Hi Ed,
>
> Thanks very much. It works now. I traverse all the imports and try to
> validate them seperately.
>
> I have another problem. I have a schema eoli.xsd, XMLSpy validates with no
> error. But eclipse xsd throws these error when i tried to validate. I am
> attaching this schema (eoli.xsd). Looks like this is valid schema.
>
> Error at line 374, in
> "file:////c:/customer/spacebel/HelloWorld/services/eoli.xsd". XSD: The
type
> of element 'http://earth.esa.int/XML/eoli#geoEle' must derive from
> 'http://earth.esa.int/XML/eoli#geoEle_._type'
> Error at line 401, in
> "file:////c:/customer/spacebel/HelloWorld/services/eoli.xsd". XSD: The
type
> of element 'http://earth.esa.int/XML/eoli#tempEle' must derive from
> 'http://earth.esa.int/XML/eoli#EX_TemporalExtendType'
> Error at line 370, in
> "file:////c:/customer/spacebel/HelloWorld/services/eoli.xsd". XSD: The
> restricted content type must accept a subset of the content accepted by
the
> base type
> Error at line 791, in
> "file:////c:/customer/spacebel/HelloWorld/services/eoli.xsd". XSD: The
> restricted content type must accept a subset of the content accepted by
the
> base type
>
> thanks,
> -muruga
>
>
> "Ed Merks" <merks@ca.ibm.com> wrote in message
> news:405ED169.43E4B2DB@ca.ibm.com...
> > Muruga,
> >
> > You have to collect diagnostics from each schema resource; it's always
> worked
> > this way. Have a look at how the XSDMainTest supports -validate by
> walking
> > each resource.
> >
> >
> > Muruga Chinnananchi wrote:
> >
> > > I am using 20040127_1738SL build. I have two schemas 1.boo.xsd 2.
> foo.xsd.
> > >
> > > boo.xsd imports "foo" schema. foo.xsd is invalid because i used
> > > type="xsd:aaaa". When i validate boo.xsd, the validate() doesn't
> populate
> > > any diagnostic error messages. But if i validate foo.xsd seperately, i
> get
> > > diagnostic error messages for unresolved type "xsd:aaaa"
> > >
> > > this combination used to work in previous build.
> > >
> > > here is the boo.xsd:
> > > <schema attributeFormDefault="qualified"
elementFormDefault="qualified"
> > > targetNamespace="http://schemas.xmlsoap.org/wsdl/"
> > > xmlns="http://www.w3.org/2001/XMLSchema"
xmlns:foo="http://foo.com">
> > > <import namespace="http://foo.com" schemaLocation="foo.xsd"/>
> > > <element name="fooElement" type="foo:fooElementType"/>
> > > </schema>
> > >
> > > here is the foo.xsd
> > > <xsd:schema targetNamespace="http://foo.com"
> > > xmlns="http://foo.com"
> > > xmlns:xsd="http://www.w3.org/2001/XMLSchema"
> > > elementFormDefault="qualified">
> > > <xsd:complexType name="fooElementType">
> > > <xsd:sequence>
> > > <xsd:element name="end" type="xsd:aaaa"/>
> > > </xsd:sequence>
> > > </xsd:complexType>
> > > </xsd:schema>
> > >
> > > thanks
> > > -muruga
> >
>
>
-
Attachment: eoli.xsd
(Size: 46.23KB, Downloaded 269 times)
|
|
|
| Re: Schema Validation Problem [message #584394 is a reply to message #39228] |
Tue, 23 March 2004 11:11 |
Ed Merks
Messages: 33140
Registered: July 2009 |
Senior Member |
|
|
Muruga,
These all appear to be legitimate errors that XMLSpy overlooked.
Muruga Chinnananchi wrote:
> oops i forgot to attach that schema file.
>
> thanks
> -muruga
>
> "Muruga Chinnananchi" <cipher8000@yahoo.com> wrote in message
> news:c3nurp$r8$1@eclipse.org...
> > Hi Ed,
> >
> > Thanks very much. It works now. I traverse all the imports and try to
> > validate them seperately.
> >
> > I have another problem. I have a schema eoli.xsd, XMLSpy validates with no
> > error. But eclipse xsd throws these error when i tried to validate. I am
> > attaching this schema (eoli.xsd). Looks like this is valid schema.
> >
> > Error at line 374, in
> > "file:////c:/customer/spacebel/HelloWorld/services/eoli.xsd". XSD: The
> type
> > of element 'http://earth.esa.int/XML/eoli#geoEle' must derive from
> > 'http://earth.esa.int/XML/eoli#geoEle_._type'
> > Error at line 401, in
> > "file:////c:/customer/spacebel/HelloWorld/services/eoli.xsd". XSD: The
> type
> > of element 'http://earth.esa.int/XML/eoli#tempEle' must derive from
> > 'http://earth.esa.int/XML/eoli#EX_TemporalExtendType'
> > Error at line 370, in
> > "file:////c:/customer/spacebel/HelloWorld/services/eoli.xsd". XSD: The
> > restricted content type must accept a subset of the content accepted by
> the
> > base type
> > Error at line 791, in
> > "file:////c:/customer/spacebel/HelloWorld/services/eoli.xsd". XSD: The
> > restricted content type must accept a subset of the content accepted by
> the
> > base type
> >
> > thanks,
> > -muruga
> >
> >
> > "Ed Merks" <merks@ca.ibm.com> wrote in message
> > news:405ED169.43E4B2DB@ca.ibm.com...
> > > Muruga,
> > >
> > > You have to collect diagnostics from each schema resource; it's always
> > worked
> > > this way. Have a look at how the XSDMainTest supports -validate by
> > walking
> > > each resource.
> > >
> > >
> > > Muruga Chinnananchi wrote:
> > >
> > > > I am using 20040127_1738SL build. I have two schemas 1.boo.xsd 2.
> > foo.xsd.
> > > >
> > > > boo.xsd imports "foo" schema. foo.xsd is invalid because i used
> > > > type="xsd:aaaa". When i validate boo.xsd, the validate() doesn't
> > populate
> > > > any diagnostic error messages. But if i validate foo.xsd seperately, i
>
> > get
> > > > diagnostic error messages for unresolved type "xsd:aaaa"
> > > >
> > > > this combination used to work in previous build.
> > > >
> > > > here is the boo.xsd:
> > > > <schema attributeFormDefault="qualified"
> elementFormDefault="qualified"
> > > > targetNamespace="http://schemas.xmlsoap.org/wsdl/"
> > > > xmlns="http://www.w3.org/2001/XMLSchema"
> xmlns:foo="http://foo.com">
> > > > <import namespace="http://foo.com" schemaLocation="foo.xsd"/>
> > > > <element name="fooElement" type="foo:fooElementType"/>
> > > > </schema>
> > > >
> > > > here is the foo.xsd
> > > > <xsd:schema targetNamespace="http://foo.com"
> > > > xmlns="http://foo.com"
> > > > xmlns:xsd="http://www.w3.org/2001/XMLSchema"
> > > > elementFormDefault="qualified">
> > > > <xsd:complexType name="fooElementType">
> > > > <xsd:sequence>
> > > > <xsd:element name="end" type="xsd:aaaa"/>
> > > > </xsd:sequence>
> > > > </xsd:complexType>
> > > > </xsd:schema>
> > > >
> > > > thanks
> > > > -muruga
> > >
> >
> >
>
> Name: eoli.xsd
> eoli.xsd Type: unspecified type (application/octet-stream)
> Encoding: x-uuencode
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
Goto Forum:
Current Time: Tue Apr 23 09:35:11 GMT 2024
Powered by FUDForum. Page generated in 0.04091 seconds |
] 
Search
Help
Register
Login
Home
