Yes, I was thinking of that, but I ran a test program with 
a URIResolver which logs it's calls to resolve(), and it seems as 
though the problem is not there now, so I was wondering if it was
fixed.  If it was fixed, then I'm wondering why the bug is open...

  -Chris


> -----Original Message-----
> From: Sal Mangano [mailto:[EMAIL PROTECTED] 
> Sent: Monday, July 12, 2004 1:44 PM
> To: [EMAIL PROTECTED]
> Subject: RE: Is the document() function still broken? i.e. Bug #2425
> 
> 
> You may be able to cache the document in a variable in the 
> mean time, no?
> 
> -Sal 
> 
> 
> > -----Original Message-----
> > From: Wolf, Chris (IT) [mailto:[EMAIL PROTECTED] 
> > Sent: Monday, July 12, 2004 11:50 AM
> > To: [EMAIL PROTECTED]
> > Subject: Is the document() function still broken? i.e. Bug #2425
> > 
> > 
> > I ask because we are using XSL to generate HTML on the fly, so 
> > performance is top priority.  Even though this bug (#2425) does 
> > not manifest in a way that breaks XSLT functionality, the fact 
> > that it will cause the referred-to document to be opened upon 
> > EACH reference effectively makes document() unusable for us.
> > 
> > Also, does this bug (2425) apply when using XSLTC?
> > 
> > We are using Xalan-2.6.0
> > 
> > Regards,
> > 
> > Chris Wolf 
> > --------------------------------------------------------
> >  
> > NOTICE: If received in error, please destroy and notify 
> > sender.  Sender does not waive confidentiality or privilege, 
> > and use is prohibited. 
> >  
> > 
> > 
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> > 
> > 
> > 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
--------------------------------------------------------
 
NOTICE: If received in error, please destroy and notify sender.  Sender does not waive 
confidentiality or privilege, and use is prohibited. 
 

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to