I tried the XPathDirectory generator. It seems like
using it will improve performance, but I don't think
the performance boost will be enough. It was
originally taking around 14 seconds to process the
process around 30 XML files. With the XPathDirectory
generator, it takes around 7 seconds. However
On Thu, Jan 16, 2003 at 03:11:37PM -0800, icewind wrote:
> Let me describe what I am doing:
>
> I have a directory that contains .xml files. In my
> sitemap, I have a pipeline that starts with a
> DirectoryGenerator on this directory. I then have a
> transformation that takes the directorygenerato
ctModel, src, par);
}
public void recycle() {
this.par = null;
super.recycle();
}
}
hope, that will help you. Perhaps you can submit your DirectoryAggregator to
the cocoon project.
Christoph Gaffga
[EMAIL PROTECTED]
From: "icewind" <[EMAIL PROTECTED]>
Subject: Re: xin
The XIncludeTransformer parses the included file into DOM,
and then streams the included part back into SAX. In my case
I have 1000 pages including parts of 10 others so I hacked
the XIncludeTransformer to keep the DOMs of those 10 pages in
memory. This is not the best solution but it's fastee,
Hi,
We had the same Problem, instead of aggregating all files from a directory
we had to aggregate all files/components from a list in our DB.
The only solution we found, that would make sence in terms of perfomance,
was to write our own Aggregator. You could simply extend Cocoon Default
Aggregato
