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
astee,
you should probably look at aggregators instead
(I had to deal with legacy XSP from Cocoon 1.x).
Artur...
> -Original Message-
> From: icewind [mailto:[EMAIL PROTECTED]]
> Sent: January 16, 2003 6:12 PM
> To: [EMAIL PROTECTED]
> Subject: xinclude performance iss
: <[EMAIL PROTECTED]>
Sent: Friday, January 17, 2003 12:11 AM
Subject: xinclude performance issues,
> 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
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 directorygenerator's
output and puts some xi:include tags with xpointers to
some tags
