Hi Jos,
I've already written my own Transformer (extends AbstractSAXTransformer)
that currently takes the output of the default cocoon xsl transformer (via the
sitemap) and performs subsequent, non-xsl transforms, writes the results to
file and generates the returned web-page
e.g.
<map:match pattern="*/*/*In/*/*In.flow/*" >
<map:generate src="inputs/{4}" />
<map:transform src="xsl/{3}InAdapter.xsl">
<map:parameter name="instanceName" value="{2}"/>
</map:transform>
<map:transform type="SPARQLinTrans">
<map:parameter name="inputFile" value="{4}"/>
<map:parameter name="SPARQLFlow" value="{5}"/>
</map:transform>
<map:serialize type="xhtml"/>
</map:match>
I'm currently heading in the direction of just adding the initial xsl
transformation as part of my own Transformer's duties (I think your option 3)
so that it can hopefully handle the larger files, but I was wondering if there
might be a way to easily keep things 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:[email protected]]
> Sent: Monday, May 10, 2010 8:39 AM
> To: [email protected]
> 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 with it (transforming, for instance)
> - write output to a file
>
> Jos
>
> On Mon, 2010-05-10 at 08:23 -0500, Schmitz, Jeffrey A wrote:
> > Correct, it's not being turned into a web page. Is a SAX pipeline
> part of Cocoon? I'm still on Cocoon 2.1, but I've never heard that
> term specifically, I thought the default generator did use SAX.
> >
> > > -----Original Message-----
> > > From: Jos Snellings [mailto:[email protected]]
> > > Sent: Saturday, May 08, 2010 12:06 AM
> > > To: [email protected]
> > > 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 inputs, a SAX pipeline
> is
> > > the way to go.
> > >
> > > Jos
> > >
> > > On Fri, 2010-05-07 at 18:14 -0500, Schmitz, Jeffrey A wrote:
> > > > 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 make Cocoon perform the transform for me?
> > > >
> > > >
> > > >
> > > > Thanks,
> > > > Jeff
> > > >
> > > >
> > >
> > >
> > >
> > > -------------------------------------------------------------------
> --
> > > To unsubscribe, e-mail: [email protected]
> > > For additional commands, e-mail: [email protected]
> >
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
