Karr, David wrote:
-----Original Message-----
From: Steve Loughran [mailto:[EMAIL PROTECTED]
Sent: Friday, November 09, 2007 2:49 AM
To: Ant Users List
Subject: Re: Xslt when run from other dir from maven gets
"Provider for javax.xml.transform.TransformerFactory cannot be found"
Karr, David wrote:
Before I implemented the reference to the "xslt" task, the build
script previously used the "xmltask" library to do the same
thing, and
that worked well enough, both directly in the build script
directory
and remotely using maven. I'm trying to get it to work with XSLT
because the xmltask solution gets OutOfMemory exceptions
for some of
the larger test cases.
so does <xslt> on java5 with the bundled XSL engine. Try
running Ant with more memory by setting ANT_OPTS to -DXmx256m
I tried setting ANT_OPTS all the way up to -Dxmx1536m, and it seemed to
make no difference. I wonder if this is some sort of infinite loop
problem with xmltask. I only saw it do it so far in one test case. It
completed for the others.
1. There is this other bit of memory, PermGenHeapSpace, which can also
lead to OOM exceptions, and it needs to be set up with its own -X
option, on Sun's JVM.
I've recently switched to using BEA's JRockit JVM ;it doesnt have a
separate option for that space, and is far less memory hungry in 64-bit
mode. As these JVMs are free to use, try grabbing it.
2. Try switching away from the java5 XSL engine to xalan proper, by
grabbing a version of xalan from http://xml.apache.org/ and sticking it
in ANT_HOME/lib. This will switch most XML tasks under ant to the new
xsl engine, which is less memory hungry
--
Steve Loughran http://www.1060.org/blogxter/publish/5
Author: Ant in Action http://antbook.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
