Hello again,
I've been playing around trying to isolate the cause of those NPEs. I
shortened the pipeline to test the XSLT sheet and the serializer. This
scenario works:
<map:pipeline>
<map:match pattern="*2.xml">
<map:generate src="{1}2.xml"/>
<map:transform src="final.xslt"/>
<map:serialize type="xls"/>
</map:match>
</map:pipeline>
The XML file used above was originally generated from my previous
example:
<map:pipeline>
<map:match pattern="*.xml">
<map:generate src="{1}.xml"/>
<map:transform type="sql">
<map:parameter name="use-connection" value="seclog"/>
</map:transform>
<map:transform src="test.xslt"/>
<map:transform src="output.xslt"/>
<!-- the xml file above came from the below transformer -->
<map:transform src="convert.xslt"/>
<map:transform src="final.xslt"/>
<map:serialize type="xls"/>
</map:match>
</map:pipeline>
Note that the short pipeline works great (the Excel file works
wonderfully). The long pipeline does now work (I get the NPEs from my
previous post). Yet the short pipeline uses XML generated by the long
pipeline, plus the same final XSLT file and the same serializer.
Any ideas at all? I'm getting into areas of cocoon I don't quite
understand.
Thanks so much,
Seth
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>
