The problem was down to the code that was in the for-each loop accessing a
variable which wasn't visible to the template that replaced the loop.
As a side note, we've been getting some rather interesting stack traces
today though - 84 students on the module, all trying to test their solutions
before submitting, on a dedicated Debian server running Tomcat and basically
nothing else, with 16GB of RAM. And we got out of memory errors ;)
-----
Gareth Howells, CertHE (Dunelm), BCS
CEO, GForce Industries
gareth(_at_)gforce-industries(_dot_)co(_dot_)uk
07862725134
GForce Industries
86, Warwick Avenue,
Quorn,
Loughborough,
LEICS.
LE12 8HE
----- Original Message -----
From: "Michael Kay" <mike(_at_)saxonica(_dot_)com>
To: <xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com>
Sent: Thursday, December 13, 2007 6:11 PM
Subject: RE: [xsl] Problem with using xsl:variable within a template in
XSL1.0
Now that I've converted the stylesheet to using
templates these statements are causing a stack trace.
A stack trace can mean two things. Either your XSLT processor has crashed,
or the XSLT processor has notified an error to the application and the
application, instead of displaying the error message neatly to the user,
has
crashed out. The fact that you saw a stack trace therefore gives us no
useful information: we need to know what caused it and what the message
was.
Michael Kay
http://www.saxonica.com/
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--