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/20 20:07:48 UTC
Xerces1.2.1 Problems
I discovered the following problems with Xerces 1.2.1:
1.) I cannot successfully import the Xerces.jar from the binary distribution
of Xerces 1.2.1 into my Visual Age 3.5 project. The import process aborts
while importing a class file from org/apache/xerces/utils/regex/. I
proceeded to import the class files in stages, and eventually found out that
Add failed: [.class file mismatch] Cannot add
org.apache.xerces.utils.regex.RegularExpression$Context since its enclosing
type does not define it.
Huh?
2.) Instead of importing Xerces.jar into my project, I tried to import the
source directory, and the import was apparently successful. However, on
running my application, Xerces complains that my schema (which validates
documents under 1.2.0) has a bunch of schema errors of the general form:
Schema error: simpleType not found : Foo
Schema error: could not resolve the type or get a null validator for
datatype : my:Foo
All of the types not found have some things in common -- They are all
simpleType, and they are all defined in a low-level common file that is two
levels removed from the top-level schema file that is handed over to the
parser. Not all of the simpleTypes defined in the low-level file flag an
error (i.e., some are OK). Also, none of the complexTypes in the low-level
file flag an error (i.e., they are all OK).
3.) Changing the order of includes in the top-level schema file causes some
more types in the low-level file to flag errors. This surprised me as I
didn't expect that changing the order of includes would have an adverse
effect on the schema.
Any clues?
Ramesh
Re: Xerces1.2.1 Problems
Posted by Eric Ye <er...@locus.apache.org>.
Would you mind posting your schema again?
_____
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 4:54 PM
Subject: Re: Xerces1.2.1 Problems
> I posted this a while ago, but got a response only to my first point, but
> not the second and third points (unrelated to the first one). Has anybody
> else run into problems with nested includes (greater than one level deep)?
> The schema in question validates fine with Xerces 1.2.0, but not with
1.2.1.
>
> Ramesh
>
>
> on 10/20/00 11:07 AM, Ramesh Gupta at ramesh@enode.com wrote:
>
> > 2.) {snip} Xerces [1.2.1] complains that my schema (which validates
> > documents under 1.2.0) has a bunch of schema errors of the general form:
> > Schema error: simpleType not found : Foo
> > Schema error: could not resolve the type or get a null validator for
> > datatype : my:Foo
> >
> > All of the types not found have some things in common -- They are all
> > simpleType, and they are all defined in a low-level common file that is
two
> > levels removed from the top-level schema file that is handed over to the
> > parser. Not all of the simpleTypes defined in the low-level file flag an
> > error (i.e., some are OK). Also, none of the complexTypes in the
low-level
> > file flag an error (i.e., they are all OK).
> >
> > 3.) Changing the order of includes in the top-level schema file causes
some
> > more types in the low-level file to flag errors. This surprised me as I
> > didn't expect that changing the order of includes would have an adverse
> > effect on the schema.
> >
> > Any clues?
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
> For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
>
>
Re: Xerces1.2.1 Problems
Posted by Eric Ye <er...@locus.apache.org>.
I've consulted with Jeffrey Rodriguez on this, we fixed the underlying
datatype registry architecture in the CVS, the problem should be gone now.
_____
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 4:54 PM
Subject: Re: Xerces1.2.1 Problems
> I posted this a while ago, but got a response only to my first point, but
> not the second and third points (unrelated to the first one). Has anybody
> else run into problems with nested includes (greater than one level deep)?
> The schema in question validates fine with Xerces 1.2.0, but not with
1.2.1.
>
> Ramesh
>
>
> on 10/20/00 11:07 AM, Ramesh Gupta at ramesh@enode.com wrote:
>
> > 2.) {snip} Xerces [1.2.1] complains that my schema (which validates
> > documents under 1.2.0) has a bunch of schema errors of the general form:
> > Schema error: simpleType not found : Foo
> > Schema error: could not resolve the type or get a null validator for
> > datatype : my:Foo
> >
> > All of the types not found have some things in common -- They are all
> > simpleType, and they are all defined in a low-level common file that is
two
> > levels removed from the top-level schema file that is handed over to the
> > parser. Not all of the simpleTypes defined in the low-level file flag an
> > error (i.e., some are OK). Also, none of the complexTypes in the
low-level
> > file flag an error (i.e., they are all OK).
> >
> > 3.) Changing the order of includes in the top-level schema file causes
some
> > more types in the low-level file to flag errors. This surprised me as I
> > didn't expect that changing the order of includes would have an adverse
> > effect on the schema.
> >
> > Any clues?
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
> For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
>
>
Re: Xerces1.2.1 Problems
Posted by Ramesh Gupta <ra...@eNode.com>.
I posted this a while ago, but got a response only to my first point, but
not the second and third points (unrelated to the first one). Has anybody
else run into problems with nested includes (greater than one level deep)?
The schema in question validates fine with Xerces 1.2.0, but not with 1.2.1.
Ramesh
on 10/20/00 11:07 AM, Ramesh Gupta at ramesh@enode.com wrote:
> 2.) {snip} Xerces [1.2.1] complains that my schema (which validates
> documents under 1.2.0) has a bunch of schema errors of the general form:
> Schema error: simpleType not found : Foo
> Schema error: could not resolve the type or get a null validator for
> datatype : my:Foo
>
> All of the types not found have some things in common -- They are all
> simpleType, and they are all defined in a low-level common file that is two
> levels removed from the top-level schema file that is handed over to the
> parser. Not all of the simpleTypes defined in the low-level file flag an
> error (i.e., some are OK). Also, none of the complexTypes in the low-level
> file flag an error (i.e., they are all OK).
>
> 3.) Changing the order of includes in the top-level schema file causes some
> more types in the low-level file to flag errors. This surprised me as I
> didn't expect that changing the order of includes would have an adverse
> effect on the schema.
>
> Any clues?