> If Myriam or I can fix this in the next day or two, can you switch to a
> current CVS build or does that bring with it other problems?
I don't know yet! But that certainly would be nice. The only other
unresolved issue with the current build (for me) is how to implement my
simple ProcessorSpecific interface (see earlier message in thread).
I'm trying to make this "product" mostly pluggable with JAXP, so I have an
interest in supporting both SAXON and Xalan, but I only *need* to make sure
one of them works so that I can ship a default.
Thanks,
Evan
> -----Original Message-----
> From: Gary L Peskin [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, August 16, 2001 4:11 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Two show-stopping bugs re: the document() function, in
> Xalan 2.1.0
>
>
> Evan --
>
> If Myriam or I can fix this in the next day or two, can you switch to a
> current CVS build or does that bring with it other problems?
>
> Gary
>
> Evan Lenz wrote:
> >
> > Hi Gary,
> >
> > Excellent explanation. The Recommendation's recursive definition of the
> > document() function certainly can be misleading :)
> >
> > > So Myriam, your analysis was correct and this is a bug and Evan should
> > > enter it into Bugzilla, please.
> >
> > I would, but I'm getting a "Bugzilla is broken" message.
> >
> > > As a workaround, Evan, if all of the nodes in the node-set
> have the same
> > > Base URI, you can specify that node-set as the second argument to the
> > > document function and all should work okay. If the nodes in the first
> > > argument node-set have different Base URIs, you're basically screwed
> > > until we fix the bug.
> >
> > Actually, I'm screwed anyway :) I'm not the one writing the
> XSLT; I don't
> > have control over that. I've already begun trying to switch to
> SAXON (which
> > is bringing its own headaches in trying to run with Tomcat...)
> >
> > Any other JAXP-compliant XSLT processors out there?
> >
> > Thanks for all your help, Gary.
> >
> > Evan Lenz
> > XYZFind Corp.