Thank you for the information. I used the log transformer and compared the
output in the view and the pipelines. They are the same .
I compared the logs at the following points
1.After the generate statement in the pipeline, first statement in the view
2.After transform in the view and pipeline
3.After serialize in the view and pipeline(This did not yield any output).
The logs are the same in both the view and pipeline at all points.
I am wondering having the serialize as the last statement in the sitemap match
or view does matter... like seralize to xls(HSSLSerializer) is the last
statement in the view but in my match pipeles its not the last statement. Can
someone tell me if this matters. Below is my complete match pipeline
<map:match pattern="security.xsp">
<map:act type="validator">
<map:parameter name="descriptor" value="descriptor.xml"/>
<map:generate type="serverpages"
src="securityresult.xsp" label="raw"/
>
<map:transform
src="context://historyserver/styles/page2xls.xsl"/>
<map:serialize type="xls"/>
</map:act>
<map:generate src="quotehistory.xsp" type="serverpages"/>
<map:transform src="context:/historyserver/styles/search.xsl"/>
<map:serialize/>
</map:match>
On Tuesday 09 March 2004 12:02 pm, Tim Larson wrote:
> On Tue, Mar 09, 2004 at 10:35:19AM -0500, Anna Bikkina wrote:
> > I am using serverpages generator to genarate xml from the xsp's. I use
> > the same xsp in both the cases. I am wondering what difference could be
> > there in the generated SAX events. The only change in my sitemap in both
> > the match statements is the transformer and the serializer after the
> > generator.
> >
> > I got the view from the generator and serialized to xls and checked it.
> > It looks perfect. As I said when I copy this file to a location in my
> > machine and use it instead of the generator and then have the
> > page2xls.xsl tranformer and seriliaze the tranformed output using
> > HSSSerializer(xls) it works.
> >
> > I changed my match pipeline in the sitemap
> > <map:generate src="security.xsp" type="serverpages" label="raw"/>
> > <map:transform
> > src="context:/historyserver/styles/page2xls.xsl"/> <map:serialize
> > type="xls"/>
> >
> > My view looks like this
> > <map:view lable="raw" name="raw">
> > <map:tranform src="context:/historyserver/styles/page2xls.xsl"/>
> > <map:serialize type="xls"/>
> > </map:view>
> >
> > I am wondering why my view is working and my match pipeline is not
> > working. They are doing just the same thing. Can you please tell me what
> > I am missing here.
> >
> > Thanks in advance,
> > Anna.
>
> The LogTransformer would be very helpful to debug this. Put a log
> transformer between each step to record the stages of the SAX event
> stream into separate files. Then use diff, WinMerge, Meld, XXDiff or
> whatever tool you like to compare the corresponding log files from your
> working and non-working pipelines. Report to this list what the
> differences are and someone may be able to diagnose the problem and
> offer a solution.
>
> Documentation for the LogTransformer is at the top of this page:
> http://wiki.cocoondev.org/Wiki.jsp?page=Transformer
> BTW, the LogTransformer gives more details for debugging than the
> profiling pipelines do, because the transformer records the actual
> full stream of SAX events, including namespace prefix mappings, etc.
>
> Hope this helps,
> --Tim Larson
>
> ---------------------------------------------------------------------
> 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]
