Checked in a fix for this. Please give it a try if you can and let me kow
how it works out. Did not get a chance to enter it in bugzilla, but maybe
I'll try on Monday.
Myriam
Myriam_Midy@lo
tus.com To: [EMAIL PROTECTED]
cc: (bcc: Myriam Midy/CAM/Lotus)
08/17/01 09:52 Subject: Re: Two show-stopping bugs re:
the document() function,
AM in Xalan 2.1.0
Please respond
to xalan-dev
Ok. I wasn't so confused after all. Gary, I have to look into a stylesheet
PI bug then I'll try to fix document(). If you get to it before me, please
let me know.
Thanks,
Myriam
Gary L Peskin
<garyp@firstec To: [EMAIL PROTECTED]
h.com> cc: (bcc: Myriam
Midy/CAM/Lotus)
Subject: Re: Two show-stopping
bugs re:
08/16/01 07:10 the document() function, in Xalan
2.1.0
PM
Please respond
to xalan-dev
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.