Hi Jeff,
You wrote: I guess I was under the impression that SAX based xsl transformers
didn't use much memory regardless file size, but perhaps that's not true?
It's true. However, when you do a XSLT transformation the entire XML document
needs to be available to the XSLT processor, because
to a 64 bit machine and just
allocating a huge amount of ram to Tomcat? Can this been done with
tomcat/cocoon?
-Original Message-
From: Huib Verweij [mailto:h...@home.nl]
Sent: Tuesday, May 11, 2010 3:51 AM
To: users@cocoon.apache.org
Cc: Huib Verweij
Subject: Re: Very large Generator
On Tue, May 11, 2010 at 07:56:19AM -0500, Schmitz, Jeffrey A wrote:
Thanks Huib,
I'm afraid my document is very interconnected. I'm coming to realize that
xslt has pretty much a hard limit on the size of files you can process with
it, i.e. if it can't fit into memory and you need the
[1] You might look at using Joost/STX which does streaming transforms.
It's not XSLT -- it's an xslt-like transformation language designed
for one pass processing,
so STXPath is more restricted than XPath.
http://joost.sourceforge.net/
We've used it within cocoon to extract data
: Saturday, May 08, 2010 12:06 AM
To: users@cocoon.apache.org
Subject: Re: Very large Generator file
Hi Jeff,
That depends a great deal on what you want to do exactly with the large
file. I guess you do not want to transform it into one huge web page?
In general, if you have to deal with lengthy
]
Sent: Saturday, May 08, 2010 12:06 AM
To: users@cocoon.apache.org
Subject: Re: Very large Generator file
Hi Jeff,
That depends a great deal on what you want to do exactly with the large
file. I guess you do not want to transform it into one huge web page?
In general, if you
: Monday, May 10, 2010 8:39 AM
To: users@cocoon.apache.org
Subject: RE: Very large Generator file
A SAX pipeline is part of cocoon.
Can you explain briefly what you want to do?
Consider using a cocoon-3 pipeline.
Consider using a SAX transformation:
- read xml
- do something
as they are and continue using the
default cocoon xsl tranform as the first step. Sounds like there's not?
-Original Message-
From: Jos Snellings [mailto:jos.snelli...@pandora.be]
Sent: Monday, May 10, 2010 8:39 AM
To: users@cocoon.apache.org
Subject: RE: Very large Generator file
-Original Message-
From: Jos Snellings [mailto:jos.snelli...@pandora.be]
Sent: Monday, May 10, 2010 9:30 AM
To: users@cocoon.apache.org
Subject: RE: Very large Generator file
Hi Jeff,
If you have been trying giving all the available memory to your tomcat
instance (JVM options) you
-Original Message-
From: Jos Snellings [mailto:jos.snelli...@pandora.be]
Sent: Monday, May 10, 2010 9:30 AM
To: users@cocoon.apache.org
Subject: RE: Very large Generator file
Hi Jeff,
If you have been trying giving all the available memory to your tomcat
instance (JVM
@cocoon.apache.org
Subject: RE: Very large Generator file
Yes, Jeff, my guess is that the tfactory stuff will accomplish the job
for you without complaining about memory shortage! Your tomcat instance
may have other things around increasing the memory footprint all the
time.
On Mon, 2010-05
Hello,
I was wondering if there's a way to handle very large files as inputs to the
default cocoon generator? As it is, I am getting a memory heap error when
trying to process an input file because it's so large. Am I going to have to
process it in some other manner, or is there a way to
Hi Jeff,
That depends a great deal on what you want to do exactly with the large
file. I guess you do not want to transform it into one huge web page?
In general, if you have to deal with lengthy inputs, a SAX pipeline is
the way to go.
Jos
On Fri, 2010-05-07 at 18:14 -0500, Schmitz, Jeffrey A
13 matches
Mail list logo
