yes, that's it! - and that will probably work for us. But I'm
curious, instead of this line:
pipelineUtil.processToSAX( "internal/catalog/getCatalog", null,
xmlSaxHandler.getContentHandler() );
which I'm assuming starts a new pipeline, can I just grab what the
"state" the pipeline was in before en
Actually, I found my example:
importClass( Packages.org.apache.xmlbeans.XmlBeans );
importClass( Packages.com.thinkreports.catalog.CatalogDocument );
importClass( Packages.com.thinkreports.util.XMLBeansXMLizableWrapper );
importClass(
Packages.org.apache.cocoon.components.flow.util.PipelineUtil );
Can you be more clear on what exactly you are asking? Do you want to
process a pipeline and have the result stored in an XMLBean? If that is
the case, you can use the PipelineUtil.processToSax method to call a
pipeline and fill up an XMLBean's content handler.
I have some examples of doing th
Hi,
I'd like to take the state of my current pipeline and populate an
xmlbean from this in the flowscript. Is this something that's already
easy to do? Here's what I'd like to do:
After the xsl transform, I will have a valid instance of my xmlbean.
Then
