Subjects
• Home
• Xalan extension functions
• Fomatting question serializing DOM with pretty print
• xalan with pull parser
• Cannot find the declaration
• Apache Xalan drop support to run on JRE 1 1 x
• Why does Doctype change processing of a document
• Node set to XML string via Java extensions in Xalan J: possible?
• Templates/Transformers + thread safety???
• Problem evaluating xpath with muliple prefix with different namespace
• remove an arbitrary attribute from xsl output
• Xalan3 XSLT 2 0 XPath 2 0 support?
• Problem using compiled translets with Xalan !!
• Xalan and jstl 1 1 problem with transform tag
• NullPointer in DOM2DTM getLocalName
• URIResolvers base parameter with xsltc and cascaded imports
• Performance problem for Xalan J on intel dual core
• Standard libraries in JAXP?
• Serializing a DOM tree to XML file, customize entities replacement
• Library Conflict Involving BCEL Library
• A question on how users are using <xsl:message >
• Kevin Cormier as a new Apache Xalan J committer
• Struggling to iterate over tokenized string
• Xalan count() trouble
• Problem with recursive xpath
• Error when switching to java 1 5
• document( ' ')
• Problem with Xalan2 7 0 transformation
• cr/lf options
• entity encoded XML
• can xalan transform 2 xml using one xslt?
• Xalan J JIRA defect review Monday October 16, 2006 from 2:00 to 3:30 pm ED
• xsl transform with cdata section elements
• xslt parameters not expanded
• Weird behavior of XPath evaluate()
• How to avoid <xsl:message > instruction prints stylesheet file informations ?
• Cannot find SimpleTransform subdirectory after installing Xalan J
• recover from document not found exceptions
• jdk1 5 and Xalan jar differences?
• Performance Issue
• Error/Bug adding floating point numbers
• XPathAPI: eval exp using nodes with default namespace
• modifying xalan to output invalid XML
• NullPointerException
• mege two separate xml nodes into one
• Is this a XALAN document identification bug?
• is StylesheetRoot really java io Serializable ?
• transform() fails for DOMSource but succeeds for StreamSource
• Thoughts on Transformer parameter passing
• HELP, Xalan and jstl 1 1 problem with transformer
• Problem with XPath namespace axis?
• string utils:replace deleting search string if replacement string is an HTML
• help with enumeration values pls
• xalan 2 5 1 vs 2 7 performance question
• How to insert/update in XML document
• HTML Serialization and Handling of Ampersands in HREF Attributes
• XHTML link tag stripping
• SystemId Unknown; Line #24; Column #49; java lang NullPointerException
• xpath text() help
• Apostrophe problem with xalan 2 7 0
• How to set variables in XML document?
Links
Home
Oracle database error code ...
 
Search:  
Power your search with and, or, +, -, or "some phrase" operators.
junit/xalan

junit/xalan

2003-09-30       - By Cote, Jean-Claude
Reply:     1     2     3  

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



<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2654.45">
<TITLE>junit/xalan</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=2 FACE="Arial">Hello,</FONT>
</P>

<P><FONT SIZE=2 FACE="Arial">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...
</FONT></P>

<P><FONT SIZE=2 FACE="Arial">In the input file I have properties one of which
is &lt;property name=&quot;java.class.path&quot;&gt;. 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?</FONT></P>

<P><FONT SIZE=2 FACE="Arial">test-reports:</FONT>
<BR><FONT SIZE=2 FACE="Arial">&nbsp;&nbsp;&nbsp;&nbsp; [echo] Making GridSphere
Junit Test Reports</FONT>
<BR><FONT SIZE=2 FACE="Arial">[junitreport] Using Xalan version: Xalan Java 2.4
.1</FONT>
</P>

<P><FONT SIZE=2 FACE="Arial">BUILD FAILED</FONT>
<BR><FONT SIZE=2 FACE="Arial">java.lang.StackOverflowError</FONT>
</P>

<P><FONT SIZE=2 FACE="Arial">Total time: 1 second</FONT>
<BR><FONT SIZE=2 FACE="Arial">java.lang.StackOverflowError</FONT>
</P>
<BR>

<P><FONT SIZE=2 FACE="Arial">Thanks for you help.</FONT>
<BR><FONT SIZE=2 FACE="Arial">Jean-Claude</FONT>
</P>
<BR>

</BODY>
</HTML>