You are viewing a plain text version of this content. The canonical link for it is here.
Posted to j-dev@xerces.apache.org by Ramesh Gupta <ra...@eNode.com> on 2000/10/14 03:57:53 UTC
Schema error: Couldn't find top level attribute
I have a schema split across multiple files: A top level file called
top.xsd, and a subordinate file called sub.xsd, where top.xsd <include>s
sub.xsd.
I am using Xerces 1.2.0. Everything works fine until I move a global
attribute declaration from top.xsd to sub.xsd. And then I get:
Schema error: Couldn't find top level attribute my:foo
Here is how foo is declared in sub.xsd:
<!-- ================================================== -->
<schema xmlns="http://www.w3.org/1999/XMLSchema"
xmlns:my="myNamespace"
xmlns:xlink="http://www.w3.org/1999/xlink"
targetNamespace="myNamespace"
xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance"
xsi:schemaLocation="http://www.w3.org/1999/XMLSchema
http://www.w3.org/1999/XMLSchema.xsd"
elementFormDefault="qualified"
attributeFormDefault="unqualified">
<import namespace="http://www.w3.org/1999/xlink"
schemaLocation="http://localhost/dummyXLink.xsd"/>
<!-- A whole bunch of stuff deleted -->
<attribute name="foo" type="string"/>
</schema>
<!-- ================================================== -->
Here is how foo is used in top.xsd:
<!-- ================================================== -->
<schema xmlns="http://www.w3.org/1999/XMLSchema"
xmlns:my="myNamespace"
xmlns:xlink="http://www.w3.org/1999/xlink"
targetNamespace="myNamespace"
xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance"
xsi:schemaLocation="http://www.w3.org/1999/XMLSchema
http://www.w3.org/1999/XMLSchema.xsd"
elementFormDefault="qualified"
attributeFormDefault="unqualified">
<import namespace="http://www.w3.org/1999/xlink"
schemaLocation="http://localhost/dummyXLink.xsd"/>
<include schemaLocation="http://localhost/sub.xsd"/>
<complexType name="MyComplexType">
<!-- A sequence of elements, followed by: -->
<attribute ref="my:foo" use="optional"/>
</complexType>
</schema>
<!-- ================================================== -->
If I move the attribute declaration back to top.xsd, the error goes away.
Global elements and types declared in sub.xsd are recognized just fine --
just the global attributes aren't.
Is this is bug, or am I doing something wrong somewhere?
Ramesh
Re: Schema error: Group Foo not found in the Schema
Posted by Ramesh Gupta <ra...@eNode.com>.
Sure, I verified the fixes with the Nov 11 dev snapshot, and the problems
are gone!
Thanks,
Ramesh
on 11/6/00 2:24 PM, Eric Ye at ericye@locus.apache.org wrote:
> I just check in more fixes, although I did some test myself, would you mind
> checking it again?
> _____
>
>
> Eric Ye * IBM, JTC - Silicon Valley * ericye@locus.apache.org
>
> ----- Original Message -----
> From: "Eric Ye" <er...@locus.apache.org>
> To: <xe...@xml.apache.org>
> Sent: Sunday, November 05, 2000 12:19 PM
> Subject: Re: Schema error: Group Foo not found in the Schema
>
>
>> I'll look into that.
>>
>> Best regards
>> Eric Ye
>> ----- Original Message -----
>> From: "Ramesh Gupta" <ra...@eNode.com>
>> To: <xe...@xml.apache.org>
>> Sent: Saturday, November 04, 2000 5:11 AM
>> Subject: Re: Schema error: Group Foo not found in the Schema
>>
>>
>>> Problem does not appear to be fixed in the dev snapshot from 04-Nov-2000
>>> 03:17.
>>>
>>> Ramesh
>>>
>>> on 11/2/00 5:48 PM, Eric Ye at ericye@locus.apache.org wrote:
>>>
>>>> Just checked in the fix for this one, check out the
> TraverseSchema.java
>> and
>>>> test it out.
>>>> _____
>>>>
>>>>
>>>> Eric Ye * IBM, JTC - Silicon Valley * ericye@locus.apache.org
>>>>
>>>> ----- Original Message -----
>>>> From: "Ramesh Gupta" <ra...@eNode.com>
>>>> To: <xe...@xml.apache.org>
>>>> Sent: Thursday, November 02, 2000 5:17 PM
>>>> Subject: Schema error: Group Foo not found in the Schema
>>>>
>>>>
>>>>> If a group is defined in sub.xsd and referenced from top.xsd, where
>>>> top.xsd
>>>>> includes sub.xsd, I get a Schema error: Group Foo not found in the
>> Schema.
>>>>>
>>>>> I am seeing this behavior in Xerces 1.2.1 (and I believe it was also
>> seen
>>>> in
>>>>> 1.2.0).
>>>>>
>>>>> Note that this is a different problem from the one that Eric has
>> already
>>>>> fixed.
>>>>>
>>>>> Ramesh
>>>>>
>>>>> on 10/16/00 11:37 AM, Eric Ye at ericye@locus.apache.org wrote:
>>>>>
>>>>>> Fixed in the CVS. thanks for the report
>>>>>> _____
>>>>>>
>>>>>>
>>>>>> Eric Ye * IBM, JTC - Silicon Valley * ericye@locus.apache.org
>>>>>>
>>>>>> ----- Original Message -----
>>>>>> From: "Ramesh Gupta" <ra...@eNode.com>
>>>>>> To: <xe...@xml.apache.org>
>>>>>> Sent: Friday, October 13, 2000 6:57 PM
>>>>>> Subject: Schema error: Couldn't find top level attribute
>>>>>>
>>>>>>
>>>>>>> I have a schema split across multiple files: A top level file
> called
>>>>>>> top.xsd, and a subordinate file called sub.xsd, where top.xsd
>>>> <include>s
>>>>>>> sub.xsd.
>>>>>>>
>>>>>>> I am using Xerces 1.2.0. Everything works fine until I move a
> global
>>>>>>> attribute declaration from top.xsd to sub.xsd. And then I get:
>>>>>>> Schema error: Couldn't find top level attribute my:foo
Re: Schema error: Group Foo not found in the Schema
Posted by Eric Ye <er...@locus.apache.org>.
I just check in more fixes, although I did some test myself, would you mind
checking it again?
_____
Eric Ye * IBM, JTC - Silicon Valley * ericye@locus.apache.org
----- Original Message -----
From: "Eric Ye" <er...@locus.apache.org>
To: <xe...@xml.apache.org>
Sent: Sunday, November 05, 2000 12:19 PM
Subject: Re: Schema error: Group Foo not found in the Schema
> I'll look into that.
>
> Best regards
> Eric Ye
> ----- Original Message -----
> From: "Ramesh Gupta" <ra...@eNode.com>
> To: <xe...@xml.apache.org>
> Sent: Saturday, November 04, 2000 5:11 AM
> Subject: Re: Schema error: Group Foo not found in the Schema
>
>
> > Problem does not appear to be fixed in the dev snapshot from 04-Nov-2000
> > 03:17.
> >
> > Ramesh
> >
> > on 11/2/00 5:48 PM, Eric Ye at ericye@locus.apache.org wrote:
> >
> > > Just checked in the fix for this one, check out the
TraverseSchema.java
> and
> > > test it out.
> > > _____
> > >
> > >
> > > Eric Ye * IBM, JTC - Silicon Valley * ericye@locus.apache.org
> > >
> > > ----- Original Message -----
> > > From: "Ramesh Gupta" <ra...@eNode.com>
> > > To: <xe...@xml.apache.org>
> > > Sent: Thursday, November 02, 2000 5:17 PM
> > > Subject: Schema error: Group Foo not found in the Schema
> > >
> > >
> > >> If a group is defined in sub.xsd and referenced from top.xsd, where
> > > top.xsd
> > >> includes sub.xsd, I get a Schema error: Group Foo not found in the
> Schema.
> > >>
> > >> I am seeing this behavior in Xerces 1.2.1 (and I believe it was also
> seen
> > > in
> > >> 1.2.0).
> > >>
> > >> Note that this is a different problem from the one that Eric has
> already
> > >> fixed.
> > >>
> > >> Ramesh
> > >>
> > >> on 10/16/00 11:37 AM, Eric Ye at ericye@locus.apache.org wrote:
> > >>
> > >>> Fixed in the CVS. thanks for the report
> > >>> _____
> > >>>
> > >>>
> > >>> Eric Ye * IBM, JTC - Silicon Valley * ericye@locus.apache.org
> > >>>
> > >>> ----- Original Message -----
> > >>> From: "Ramesh Gupta" <ra...@eNode.com>
> > >>> To: <xe...@xml.apache.org>
> > >>> Sent: Friday, October 13, 2000 6:57 PM
> > >>> Subject: Schema error: Couldn't find top level attribute
> > >>>
> > >>>
> > >>>> I have a schema split across multiple files: A top level file
called
> > >>>> top.xsd, and a subordinate file called sub.xsd, where top.xsd
> > > <include>s
> > >>>> sub.xsd.
> > >>>>
> > >>>> I am using Xerces 1.2.0. Everything works fine until I move a
global
> > >>>> attribute declaration from top.xsd to sub.xsd. And then I get:
> > >>>> Schema error: Couldn't find top level attribute my:foo
> > >>>>
> > >>>> Here is how foo is declared in sub.xsd:
> > >>>>
> > >>>> <!-- ================================================== -->
> > >>>> <schema xmlns="http://www.w3.org/1999/XMLSchema"
> > >>>> xmlns:my="myNamespace"
> > >>>> xmlns:xlink="http://www.w3.org/1999/xlink"
> > >>>> targetNamespace="myNamespace"
> > >>>> xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance"
> > >>>> xsi:schemaLocation="http://www.w3.org/1999/XMLSchema
> > >>>> http://www.w3.org/1999/XMLSchema.xsd"
> > >>>> elementFormDefault="qualified"
> > >>>> attributeFormDefault="unqualified">
> > >>>>
> > >>>> <import namespace="http://www.w3.org/1999/xlink"
> > >>>> schemaLocation="http://localhost/dummyXLink.xsd"/>
> > >>>>
> > >>>> <!-- A whole bunch of stuff deleted -->
> > >>>>
> > >>>> <attribute name="foo" type="string"/>
> > >>>> </schema>
> > >>>> <!-- ================================================== -->
> > >>>>
> > >>>> Here is how foo is used in top.xsd:
> > >>>>
> > >>>> <!-- ================================================== -->
> > >>>> <schema xmlns="http://www.w3.org/1999/XMLSchema"
> > >>>> xmlns:my="myNamespace"
> > >>>> xmlns:xlink="http://www.w3.org/1999/xlink"
> > >>>> targetNamespace="myNamespace"
> > >>>> xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance"
> > >>>> xsi:schemaLocation="http://www.w3.org/1999/XMLSchema
> > >>>> http://www.w3.org/1999/XMLSchema.xsd"
> > >>>> elementFormDefault="qualified"
> > >>>> attributeFormDefault="unqualified">
> > >>>>
> > >>>> <import namespace="http://www.w3.org/1999/xlink"
> > >>>> schemaLocation="http://localhost/dummyXLink.xsd"/>
> > >>>> <include schemaLocation="http://localhost/sub.xsd"/>
> > >>>>
> > >>>> <complexType name="MyComplexType">
> > >>>> <!-- A sequence of elements, followed by: -->
> > >>>> <attribute ref="my:foo" use="optional"/>
> > >>>> </complexType>
> > >>>> </schema>
> > >>>> <!-- ================================================== -->
> > >>>>
> > >>>> If I move the attribute declaration back to top.xsd, the error goes
> > > away.
> > >>>> Global elements and types declared in sub.xsd are recognized just
> > > fine --
> > >>>> just the global attributes aren't.
> > >>>>
> > >>>> Is this is bug, or am I doing something wrong somewhere?
> > >>
> > >>
> > >> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
> > >> For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
> > >>
> > >>
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
> > > For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
> > >
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
> > For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
> For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
>
>
Re: Schema error: Group Foo not found in the Schema
Posted by Eric Ye <er...@locus.apache.org>.
I'll look into that.
Best regards
Eric Ye
----- Original Message -----
From: "Ramesh Gupta" <ra...@eNode.com>
To: <xe...@xml.apache.org>
Sent: Saturday, November 04, 2000 5:11 AM
Subject: Re: Schema error: Group Foo not found in the Schema
> Problem does not appear to be fixed in the dev snapshot from 04-Nov-2000
> 03:17.
>
> Ramesh
>
> on 11/2/00 5:48 PM, Eric Ye at ericye@locus.apache.org wrote:
>
> > Just checked in the fix for this one, check out the TraverseSchema.java
and
> > test it out.
> > _____
> >
> >
> > Eric Ye * IBM, JTC - Silicon Valley * ericye@locus.apache.org
> >
> > ----- Original Message -----
> > From: "Ramesh Gupta" <ra...@eNode.com>
> > To: <xe...@xml.apache.org>
> > Sent: Thursday, November 02, 2000 5:17 PM
> > Subject: Schema error: Group Foo not found in the Schema
> >
> >
> >> If a group is defined in sub.xsd and referenced from top.xsd, where
> > top.xsd
> >> includes sub.xsd, I get a Schema error: Group Foo not found in the
Schema.
> >>
> >> I am seeing this behavior in Xerces 1.2.1 (and I believe it was also
seen
> > in
> >> 1.2.0).
> >>
> >> Note that this is a different problem from the one that Eric has
already
> >> fixed.
> >>
> >> Ramesh
> >>
> >> on 10/16/00 11:37 AM, Eric Ye at ericye@locus.apache.org wrote:
> >>
> >>> Fixed in the CVS. thanks for the report
> >>> _____
> >>>
> >>>
> >>> Eric Ye * IBM, JTC - Silicon Valley * ericye@locus.apache.org
> >>>
> >>> ----- Original Message -----
> >>> From: "Ramesh Gupta" <ra...@eNode.com>
> >>> To: <xe...@xml.apache.org>
> >>> Sent: Friday, October 13, 2000 6:57 PM
> >>> Subject: Schema error: Couldn't find top level attribute
> >>>
> >>>
> >>>> I have a schema split across multiple files: A top level file called
> >>>> top.xsd, and a subordinate file called sub.xsd, where top.xsd
> > <include>s
> >>>> sub.xsd.
> >>>>
> >>>> I am using Xerces 1.2.0. Everything works fine until I move a global
> >>>> attribute declaration from top.xsd to sub.xsd. And then I get:
> >>>> Schema error: Couldn't find top level attribute my:foo
> >>>>
> >>>> Here is how foo is declared in sub.xsd:
> >>>>
> >>>> <!-- ================================================== -->
> >>>> <schema xmlns="http://www.w3.org/1999/XMLSchema"
> >>>> xmlns:my="myNamespace"
> >>>> xmlns:xlink="http://www.w3.org/1999/xlink"
> >>>> targetNamespace="myNamespace"
> >>>> xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance"
> >>>> xsi:schemaLocation="http://www.w3.org/1999/XMLSchema
> >>>> http://www.w3.org/1999/XMLSchema.xsd"
> >>>> elementFormDefault="qualified"
> >>>> attributeFormDefault="unqualified">
> >>>>
> >>>> <import namespace="http://www.w3.org/1999/xlink"
> >>>> schemaLocation="http://localhost/dummyXLink.xsd"/>
> >>>>
> >>>> <!-- A whole bunch of stuff deleted -->
> >>>>
> >>>> <attribute name="foo" type="string"/>
> >>>> </schema>
> >>>> <!-- ================================================== -->
> >>>>
> >>>> Here is how foo is used in top.xsd:
> >>>>
> >>>> <!-- ================================================== -->
> >>>> <schema xmlns="http://www.w3.org/1999/XMLSchema"
> >>>> xmlns:my="myNamespace"
> >>>> xmlns:xlink="http://www.w3.org/1999/xlink"
> >>>> targetNamespace="myNamespace"
> >>>> xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance"
> >>>> xsi:schemaLocation="http://www.w3.org/1999/XMLSchema
> >>>> http://www.w3.org/1999/XMLSchema.xsd"
> >>>> elementFormDefault="qualified"
> >>>> attributeFormDefault="unqualified">
> >>>>
> >>>> <import namespace="http://www.w3.org/1999/xlink"
> >>>> schemaLocation="http://localhost/dummyXLink.xsd"/>
> >>>> <include schemaLocation="http://localhost/sub.xsd"/>
> >>>>
> >>>> <complexType name="MyComplexType">
> >>>> <!-- A sequence of elements, followed by: -->
> >>>> <attribute ref="my:foo" use="optional"/>
> >>>> </complexType>
> >>>> </schema>
> >>>> <!-- ================================================== -->
> >>>>
> >>>> If I move the attribute declaration back to top.xsd, the error goes
> > away.
> >>>> Global elements and types declared in sub.xsd are recognized just
> > fine --
> >>>> just the global attributes aren't.
> >>>>
> >>>> Is this is bug, or am I doing something wrong somewhere?
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
> >> For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
> >>
> >>
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
> > For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
> For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
>
>
Re: Schema error: Group Foo not found in the Schema
Posted by Ramesh Gupta <ra...@eNode.com>.
Problem does not appear to be fixed in the dev snapshot from 04-Nov-2000
03:17.
Ramesh
on 11/2/00 5:48 PM, Eric Ye at ericye@locus.apache.org wrote:
> Just checked in the fix for this one, check out the TraverseSchema.java and
> test it out.
> _____
>
>
> Eric Ye * IBM, JTC - Silicon Valley * ericye@locus.apache.org
>
> ----- Original Message -----
> From: "Ramesh Gupta" <ra...@eNode.com>
> To: <xe...@xml.apache.org>
> Sent: Thursday, November 02, 2000 5:17 PM
> Subject: Schema error: Group Foo not found in the Schema
>
>
>> If a group is defined in sub.xsd and referenced from top.xsd, where
> top.xsd
>> includes sub.xsd, I get a Schema error: Group Foo not found in the Schema.
>>
>> I am seeing this behavior in Xerces 1.2.1 (and I believe it was also seen
> in
>> 1.2.0).
>>
>> Note that this is a different problem from the one that Eric has already
>> fixed.
>>
>> Ramesh
>>
>> on 10/16/00 11:37 AM, Eric Ye at ericye@locus.apache.org wrote:
>>
>>> Fixed in the CVS. thanks for the report
>>> _____
>>>
>>>
>>> Eric Ye * IBM, JTC - Silicon Valley * ericye@locus.apache.org
>>>
>>> ----- Original Message -----
>>> From: "Ramesh Gupta" <ra...@eNode.com>
>>> To: <xe...@xml.apache.org>
>>> Sent: Friday, October 13, 2000 6:57 PM
>>> Subject: Schema error: Couldn't find top level attribute
>>>
>>>
>>>> I have a schema split across multiple files: A top level file called
>>>> top.xsd, and a subordinate file called sub.xsd, where top.xsd
> <include>s
>>>> sub.xsd.
>>>>
>>>> I am using Xerces 1.2.0. Everything works fine until I move a global
>>>> attribute declaration from top.xsd to sub.xsd. And then I get:
>>>> Schema error: Couldn't find top level attribute my:foo
>>>>
>>>> Here is how foo is declared in sub.xsd:
>>>>
>>>> <!-- ================================================== -->
>>>> <schema xmlns="http://www.w3.org/1999/XMLSchema"
>>>> xmlns:my="myNamespace"
>>>> xmlns:xlink="http://www.w3.org/1999/xlink"
>>>> targetNamespace="myNamespace"
>>>> xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance"
>>>> xsi:schemaLocation="http://www.w3.org/1999/XMLSchema
>>>> http://www.w3.org/1999/XMLSchema.xsd"
>>>> elementFormDefault="qualified"
>>>> attributeFormDefault="unqualified">
>>>>
>>>> <import namespace="http://www.w3.org/1999/xlink"
>>>> schemaLocation="http://localhost/dummyXLink.xsd"/>
>>>>
>>>> <!-- A whole bunch of stuff deleted -->
>>>>
>>>> <attribute name="foo" type="string"/>
>>>> </schema>
>>>> <!-- ================================================== -->
>>>>
>>>> Here is how foo is used in top.xsd:
>>>>
>>>> <!-- ================================================== -->
>>>> <schema xmlns="http://www.w3.org/1999/XMLSchema"
>>>> xmlns:my="myNamespace"
>>>> xmlns:xlink="http://www.w3.org/1999/xlink"
>>>> targetNamespace="myNamespace"
>>>> xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance"
>>>> xsi:schemaLocation="http://www.w3.org/1999/XMLSchema
>>>> http://www.w3.org/1999/XMLSchema.xsd"
>>>> elementFormDefault="qualified"
>>>> attributeFormDefault="unqualified">
>>>>
>>>> <import namespace="http://www.w3.org/1999/xlink"
>>>> schemaLocation="http://localhost/dummyXLink.xsd"/>
>>>> <include schemaLocation="http://localhost/sub.xsd"/>
>>>>
>>>> <complexType name="MyComplexType">
>>>> <!-- A sequence of elements, followed by: -->
>>>> <attribute ref="my:foo" use="optional"/>
>>>> </complexType>
>>>> </schema>
>>>> <!-- ================================================== -->
>>>>
>>>> If I move the attribute declaration back to top.xsd, the error goes
> away.
>>>> Global elements and types declared in sub.xsd are recognized just
> fine --
>>>> just the global attributes aren't.
>>>>
>>>> Is this is bug, or am I doing something wrong somewhere?
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
>> For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
> For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
>
>
Re: Schema error: Group Foo not found in the Schema
Posted by Ramesh Gupta <ra...@eNode.com>.
This problem still exists in the dev snapshot from 04-Nov-2000 03:17. I get:
Schema error: Couldn't find top level attributeGroup my:FooAttributes. Note
that this is different from the other problem that exists:
Schema error: Group Foo not found in the Schema
Ramesh
on 11/2/00 8:24 PM, Ramesh Gupta at ramesh@enode.com wrote:
> Eric,
>
> Sorry for the piecemeal nature of these bug reports, but I just discovered
> that a similar problem exists for attributeGroup as well in 1.2.1. I haven't
> tried your latest fix for group yet.
>
> Ramesh
>
> on 11/2/00 5:48 PM, Eric Ye at ericye@locus.apache.org wrote:
>
>> Just checked in the fix for this one, check out the TraverseSchema.java and
>> test it out.
>> _____
>>
>>
>> Eric Ye * IBM, JTC - Silicon Valley * ericye@locus.apache.org
>>
>> ----- Original Message -----
>> From: "Ramesh Gupta" <ra...@eNode.com>
>> To: <xe...@xml.apache.org>
>> Sent: Thursday, November 02, 2000 5:17 PM
>> Subject: Schema error: Group Foo not found in the Schema
>>
>>
>>> If a group is defined in sub.xsd and referenced from top.xsd,
>>> where top.xsd includes sub.xsd, I get a
>>> Schema error: Group Foo not found in the Schema.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
> For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
>
>
Re: Schema error: Group Foo not found in the Schema
Posted by Ramesh Gupta <ra...@eNode.com>.
Eric,
Sorry for the piecemeal nature of these bug reports, but I just discovered
that a similar problem exists for attributeGroup as well in 1.2.1. I haven't
tried your latest fix for group yet.
Ramesh
on 11/2/00 5:48 PM, Eric Ye at ericye@locus.apache.org wrote:
> Just checked in the fix for this one, check out the TraverseSchema.java and
> test it out.
> _____
>
>
> Eric Ye * IBM, JTC - Silicon Valley * ericye@locus.apache.org
>
> ----- Original Message -----
> From: "Ramesh Gupta" <ra...@eNode.com>
> To: <xe...@xml.apache.org>
> Sent: Thursday, November 02, 2000 5:17 PM
> Subject: Schema error: Group Foo not found in the Schema
>
>
>> If a group is defined in sub.xsd and referenced from top.xsd,
>> where top.xsd includes sub.xsd, I get a
>> Schema error: Group Foo not found in the Schema.
Re: Schema error: Group Foo not found in the Schema
Posted by Eric Ye <er...@locus.apache.org>.
Just checked in the fix for this one, check out the TraverseSchema.java and
test it out.
_____
Eric Ye * IBM, JTC - Silicon Valley * ericye@locus.apache.org
----- Original Message -----
From: "Ramesh Gupta" <ra...@eNode.com>
To: <xe...@xml.apache.org>
Sent: Thursday, November 02, 2000 5:17 PM
Subject: Schema error: Group Foo not found in the Schema
> If a group is defined in sub.xsd and referenced from top.xsd, where
top.xsd
> includes sub.xsd, I get a Schema error: Group Foo not found in the Schema.
>
> I am seeing this behavior in Xerces 1.2.1 (and I believe it was also seen
in
> 1.2.0).
>
> Note that this is a different problem from the one that Eric has already
> fixed.
>
> Ramesh
>
> on 10/16/00 11:37 AM, Eric Ye at ericye@locus.apache.org wrote:
>
> > Fixed in the CVS. thanks for the report
> > _____
> >
> >
> > Eric Ye * IBM, JTC - Silicon Valley * ericye@locus.apache.org
> >
> > ----- Original Message -----
> > From: "Ramesh Gupta" <ra...@eNode.com>
> > To: <xe...@xml.apache.org>
> > Sent: Friday, October 13, 2000 6:57 PM
> > Subject: Schema error: Couldn't find top level attribute
> >
> >
> >> I have a schema split across multiple files: A top level file called
> >> top.xsd, and a subordinate file called sub.xsd, where top.xsd
<include>s
> >> sub.xsd.
> >>
> >> I am using Xerces 1.2.0. Everything works fine until I move a global
> >> attribute declaration from top.xsd to sub.xsd. And then I get:
> >> Schema error: Couldn't find top level attribute my:foo
> >>
> >> Here is how foo is declared in sub.xsd:
> >>
> >> <!-- ================================================== -->
> >> <schema xmlns="http://www.w3.org/1999/XMLSchema"
> >> xmlns:my="myNamespace"
> >> xmlns:xlink="http://www.w3.org/1999/xlink"
> >> targetNamespace="myNamespace"
> >> xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance"
> >> xsi:schemaLocation="http://www.w3.org/1999/XMLSchema
> >> http://www.w3.org/1999/XMLSchema.xsd"
> >> elementFormDefault="qualified"
> >> attributeFormDefault="unqualified">
> >>
> >> <import namespace="http://www.w3.org/1999/xlink"
> >> schemaLocation="http://localhost/dummyXLink.xsd"/>
> >>
> >> <!-- A whole bunch of stuff deleted -->
> >>
> >> <attribute name="foo" type="string"/>
> >> </schema>
> >> <!-- ================================================== -->
> >>
> >> Here is how foo is used in top.xsd:
> >>
> >> <!-- ================================================== -->
> >> <schema xmlns="http://www.w3.org/1999/XMLSchema"
> >> xmlns:my="myNamespace"
> >> xmlns:xlink="http://www.w3.org/1999/xlink"
> >> targetNamespace="myNamespace"
> >> xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance"
> >> xsi:schemaLocation="http://www.w3.org/1999/XMLSchema
> >> http://www.w3.org/1999/XMLSchema.xsd"
> >> elementFormDefault="qualified"
> >> attributeFormDefault="unqualified">
> >>
> >> <import namespace="http://www.w3.org/1999/xlink"
> >> schemaLocation="http://localhost/dummyXLink.xsd"/>
> >> <include schemaLocation="http://localhost/sub.xsd"/>
> >>
> >> <complexType name="MyComplexType">
> >> <!-- A sequence of elements, followed by: -->
> >> <attribute ref="my:foo" use="optional"/>
> >> </complexType>
> >> </schema>
> >> <!-- ================================================== -->
> >>
> >> If I move the attribute declaration back to top.xsd, the error goes
away.
> >> Global elements and types declared in sub.xsd are recognized just
fine --
> >> just the global attributes aren't.
> >>
> >> Is this is bug, or am I doing something wrong somewhere?
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
> For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
>
>
Schema error: Group Foo not found in the Schema
Posted by Ramesh Gupta <ra...@eNode.com>.
If a group is defined in sub.xsd and referenced from top.xsd, where top.xsd
includes sub.xsd, I get a Schema error: Group Foo not found in the Schema.
I am seeing this behavior in Xerces 1.2.1 (and I believe it was also seen in
1.2.0).
Note that this is a different problem from the one that Eric has already
fixed.
Ramesh
on 10/16/00 11:37 AM, Eric Ye at ericye@locus.apache.org wrote:
> Fixed in the CVS. thanks for the report
> _____
>
>
> Eric Ye * IBM, JTC - Silicon Valley * ericye@locus.apache.org
>
> ----- Original Message -----
> From: "Ramesh Gupta" <ra...@eNode.com>
> To: <xe...@xml.apache.org>
> Sent: Friday, October 13, 2000 6:57 PM
> Subject: Schema error: Couldn't find top level attribute
>
>
>> I have a schema split across multiple files: A top level file called
>> top.xsd, and a subordinate file called sub.xsd, where top.xsd <include>s
>> sub.xsd.
>>
>> I am using Xerces 1.2.0. Everything works fine until I move a global
>> attribute declaration from top.xsd to sub.xsd. And then I get:
>> Schema error: Couldn't find top level attribute my:foo
>>
>> Here is how foo is declared in sub.xsd:
>>
>> <!-- ================================================== -->
>> <schema xmlns="http://www.w3.org/1999/XMLSchema"
>> xmlns:my="myNamespace"
>> xmlns:xlink="http://www.w3.org/1999/xlink"
>> targetNamespace="myNamespace"
>> xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance"
>> xsi:schemaLocation="http://www.w3.org/1999/XMLSchema
>> http://www.w3.org/1999/XMLSchema.xsd"
>> elementFormDefault="qualified"
>> attributeFormDefault="unqualified">
>>
>> <import namespace="http://www.w3.org/1999/xlink"
>> schemaLocation="http://localhost/dummyXLink.xsd"/>
>>
>> <!-- A whole bunch of stuff deleted -->
>>
>> <attribute name="foo" type="string"/>
>> </schema>
>> <!-- ================================================== -->
>>
>> Here is how foo is used in top.xsd:
>>
>> <!-- ================================================== -->
>> <schema xmlns="http://www.w3.org/1999/XMLSchema"
>> xmlns:my="myNamespace"
>> xmlns:xlink="http://www.w3.org/1999/xlink"
>> targetNamespace="myNamespace"
>> xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance"
>> xsi:schemaLocation="http://www.w3.org/1999/XMLSchema
>> http://www.w3.org/1999/XMLSchema.xsd"
>> elementFormDefault="qualified"
>> attributeFormDefault="unqualified">
>>
>> <import namespace="http://www.w3.org/1999/xlink"
>> schemaLocation="http://localhost/dummyXLink.xsd"/>
>> <include schemaLocation="http://localhost/sub.xsd"/>
>>
>> <complexType name="MyComplexType">
>> <!-- A sequence of elements, followed by: -->
>> <attribute ref="my:foo" use="optional"/>
>> </complexType>
>> </schema>
>> <!-- ================================================== -->
>>
>> If I move the attribute declaration back to top.xsd, the error goes away.
>> Global elements and types declared in sub.xsd are recognized just fine --
>> just the global attributes aren't.
>>
>> Is this is bug, or am I doing something wrong somewhere?
Re: Schema error: Couldn't find top level attribute
Posted by Eric Ye <er...@locus.apache.org>.
Fixed in the CVS. thanks for the report
_____
Eric Ye * IBM, JTC - Silicon Valley * ericye@locus.apache.org
----- Original Message -----
From: "Ramesh Gupta" <ra...@eNode.com>
To: <xe...@xml.apache.org>
Sent: Friday, October 13, 2000 6:57 PM
Subject: Schema error: Couldn't find top level attribute
> I have a schema split across multiple files: A top level file called
> top.xsd, and a subordinate file called sub.xsd, where top.xsd <include>s
> sub.xsd.
>
> I am using Xerces 1.2.0. Everything works fine until I move a global
> attribute declaration from top.xsd to sub.xsd. And then I get:
> Schema error: Couldn't find top level attribute my:foo
>
> Here is how foo is declared in sub.xsd:
>
> <!-- ================================================== -->
> <schema xmlns="http://www.w3.org/1999/XMLSchema"
> xmlns:my="myNamespace"
> xmlns:xlink="http://www.w3.org/1999/xlink"
> targetNamespace="myNamespace"
> xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance"
> xsi:schemaLocation="http://www.w3.org/1999/XMLSchema
> http://www.w3.org/1999/XMLSchema.xsd"
> elementFormDefault="qualified"
> attributeFormDefault="unqualified">
>
> <import namespace="http://www.w3.org/1999/xlink"
> schemaLocation="http://localhost/dummyXLink.xsd"/>
>
> <!-- A whole bunch of stuff deleted -->
>
> <attribute name="foo" type="string"/>
> </schema>
> <!-- ================================================== -->
>
> Here is how foo is used in top.xsd:
>
> <!-- ================================================== -->
> <schema xmlns="http://www.w3.org/1999/XMLSchema"
> xmlns:my="myNamespace"
> xmlns:xlink="http://www.w3.org/1999/xlink"
> targetNamespace="myNamespace"
> xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance"
> xsi:schemaLocation="http://www.w3.org/1999/XMLSchema
> http://www.w3.org/1999/XMLSchema.xsd"
> elementFormDefault="qualified"
> attributeFormDefault="unqualified">
>
> <import namespace="http://www.w3.org/1999/xlink"
> schemaLocation="http://localhost/dummyXLink.xsd"/>
> <include schemaLocation="http://localhost/sub.xsd"/>
>
> <complexType name="MyComplexType">
> <!-- A sequence of elements, followed by: -->
> <attribute ref="my:foo" use="optional"/>
> </complexType>
> </schema>
> <!-- ================================================== -->
>
> If I move the attribute declaration back to top.xsd, the error goes away.
> Global elements and types declared in sub.xsd are recognized just fine --
> just the global attributes aren't.
>
> Is this is bug, or am I doing something wrong somewhere?
>
> Ramesh
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
> For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
>
>