Here's what I think is going on:
It appears not to be specific to "xalan:evaluate", but rather, there appears
to be a more general problem evaluating an XPath expression on the source
XML document of a transformation from within a for-each loop on the results
of a xalan:tokenize extension function call. The attached files demonstrate
the error.
Regards,
Rick Bullotta
Lighthammer
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, October 02, 2001 2:50 PM
To: [EMAIL PROTECTED]
Subject: RE: Xalan 2.2 D11 - Change in xalan:evaluate - Bug?
Rick,
What exactly is the problem? Can you include a zip file with the xsl and
xml files?
Thanks,
Myriam
"Rick Bullotta"
<rick.bullotta@lighth To:
<[EMAIL PROTECTED]>
ammer.com> cc: (bcc: Myriam
Midy/CAM/Lotus)
Subject: RE: Xalan 2.2
D11 - Change
10/02/01 02:45 PM in xalan:evaluate - Bug?
Please respond to
xalan-dev
Ignore last posting! You can already tell why...<g> Cut and paste strikes
again...the evaluate issue still exists, though.
-----Original Message-----
From: Rick Bullotta [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, October 02, 2001 2:27 PM
To: [EMAIL PROTECTED]
Subject: RE: Xalan 2.2 D11 - Change in xalan:evaluate - Bug?
As a followup, the issue appears elsewhere, for example, given the
following
XML document:
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<Rowsets DateCreated="2001-10-02 12:59:13" EndDate="2001-10-02 12:59:13"
StartDate="2001-10-02 11:59:13" Version="9.0">
<Rowset>
.....
Samples.zip
