Hi Jean-Claude,
I edited the template, which matches 'properties' nodes (<xsl:template match="properties">).
There is a line like (I don't know exactly how it looks in your file, because I did not find the original version any more):
<xsl:for-each select="property"> ... </xsl:for-each>
I changed it to:
<xsl:for-each select="property[not(@name = 'java.class.path')]"> ... </xsl:for-each>
The additional predicate takes care of skipping property "java.class.path". Regards,
Johannes
Cote, Jean-Claude wrote:
You edited junit-noframes.xsl? How did you do this? I would do the same until we find out what's going on here. Thanks
-----Original Message----- From: Johannes Lebek [mailto:[EMAIL PROTECTED] Sent: September 30, 2003 8:37 AM To: [EMAIL PROTECTED] Subject: Re: junit/xalan
Hi Jean-Claude,
I encountered the same problem at exactly the same property (java.class.path). I did not count the number ot path entries. I just saw that more than about 5000 characters as an attribute value make Xalan crash.
I worked around by editing the stylesheet: property "java.class.path" is not evaluated anymore...
Since this is no perfect solution, I'm also interested in a fix or something.
Regards,
Johannes
Cote, Jean-Claude wrote:
Hello,
I'm running a junit test using ant. It produces an xml file called TEST-org.gridlab.gridsphere.GridSphereTest.xml. I then run
a junitreport
using ant which uses xalan 2.4.1 to produce an junit-noframes.html report. All is fine until I reach somekind of limitation
with Xalan. I
think...
In the input file I have properties one of which is <property name="java.class.path">. When the value of this property
contains more
than 57 paths I get this error. Any ideas what's happening.
Is there a
limitation to the lenght of a value?
test-reports: [echo] Making GridSphere Junit Test Reports [junitreport] Using Xalan version: Xalan Java 2.4.1
BUILD FAILED java.lang.StackOverflowError
Total time: 1 second java.lang.StackOverflowError
Thanks for you help. Jean-Claude
