RE: Last Cry For Help: "Could not parse Input XML document!" XMLV alidator. [XalanJ1]

[Daryl Beattie <Da...@screamingmedia.com>]

Dear Scott,

	Please see below for my reply. And once again, thanks for your help.
:)

Sincerely,

	Daryl.

> -----Original Message-----
> From: Scott_Boag@lotus.com [mailto:Scott_Boag@lotus.com]
> Sent: Thursday, February 22, 2001 9:02 PM
> To: xalan-dev@xml.apache.org
> Subject: RE: Last Cry For Help: "Could not parse Input XML document!"
> XMLV alidator.<init> [XalanJ1]
> 
> 
> 
> Daryl Beattie <Da...@screamingmedia.com> wrote:
> > The
> > problems I am having there are being discussed in the 
> e-mail thread that
> has
> > the title "Errors to stderr/out AND no output at all AND 
> meta-data not
> > allowed".
> 
> I just checked in a fix for this, or at least part of the problem (I
> suspect it's the whole problem).  If you're not checking out 
> and building
> from the CVS, let me know and I can send you a jar to try.

	I'm not building from CVS; can I get a jar to try? [this is about
the XalanJ2 problems]

> 
> > What do you mean by the "compatibility layer"? Where can I find more
> > information about this?
> 
> I don't think this has anything to do with it.  The 
> compatibility layer is
> a jar that attempt to emulate the Xalan1 APIs in Xalan2.

	Oh, alrite. Thanks.

> 
> > java.lang.NullPointerException: ; at
> >
> org.apache.xerces.validators.common.XMLValidator.init(XMLValid
> ator.java:1535
> 
> > ); at
> >
> org.apache.xerces.validators.common.XMLValidator.<init>(XMLVal
> idator.java:40
> 1);
> 
> OK, this is great, though I'm still not certain which version 
> of Xerces.
> If I look at 1535 in the 1.2.3 version, it doesn't seem to 
> make a lot of
> sense... it's at the closing bracket of the init function.  
> It's certainly
> not version 1.3.0.

	The version information from the Xalan/Xerces that is giving the
errors is:
	>>>>>>> Xalan Version 1.2.1, XML4J Version Xerces 1.2.1<<<<<<<

> 
> > Okay, if I do this, it probably means that I have to actually
> > compile Xalan myself for the first time. :) Until now, I 
> have been using
> the
> > Jars. If you would still like me to do this after seeing 
> the above error,
> > please let me know.
> 
> Not Xalan, Xerces.
> 
> By your description and your error stack, it looks like a 
> problem with a
> parser being used multiple times, which I don't think Xalan 
> ever does (but
> which version of XalanJ1 did you say you were using?).  Or it 
> might be a
> raw threading bug in Xerces.  This is going to be a bit hard 
> to track down.

	The version information above is the information that is specific to
the errors messages I have included in previous e-mails. I haven't tested
with the 1.2.2 release, because, as I mentioned, testing is a sloooow
process. I will start such a test immediately, though.

Sincerely,

	Daryl.