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 full power of xslt you're pretty much out of luck. What about going 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 file > > 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 you can > access any node in the document, e.g. > "/very/large/path/to/some/dark/corner/of/the/XML/node". > > I'm not sure about your use-case so I don't know if it will help, but > you could try using the MultiFragmentTraxTransformer from the > cocooncomponents project on Google code. It reduces memory consumption > drastically by allowing you to specify a fragment in the XML that you > want transformed. If you have a very large document that looks like > this: > > <root> > <item/> > <item/> > .... > <item/> > </root> > > and all you want to do is transform the <item/> elements then the > MultiFragmentTraxTransformer is your friend. > > Huib. > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@cocoon.apache.org > For additional commands, e-mail: users-h...@cocoon.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@cocoon.apache.org For additional commands, e-mail: users-h...@cocoon.apache.org
