You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cocoon.apache.org by Irv Salisbury <ir...@gmail.com> on 2005/05/09 20:48:27 UTC
Log transformer, logging pipelines
In a pipeline we have for producing XML data for our forms, we'd like
to be able to debug what is happening at various points in the
pipeline. We can't use the cocoon-view stuff, as we can't call this
URL directly, and it needs a number of things setup to produce the
form, etc. I see there is a LogTransformer which is "close" to what I
need, except it produces somewhat cryptic output based on SAXEvents.
Has anyone written a LogTransformer like thing that dumps regular XML
output to a file?
Or, has anyone any other ideas on debugging these very "internal"
pipelines that can't be done with cocoon-view?
Thanks,
Irv
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: Log transformer, logging pipelines
Posted by Irv Salisbury <ir...@gmail.com>.
First, thanks for Adam's link. That is what I as looking for.
Actually, it also led me to the profiler, which seems to be even more
what I was looking for :-)
On the single transformer per map:match, I think you can get the same
effect with views, and still be able to type a URL like
cocoon-view=inclArrows.
Unfortunately, this won't work for me as I am deep in the forms
pipelines and they only get called as the result of a cocoon forms
submission, and faking that out is a lot tougher.
Irv
On 5/9/05, Chris Maloney <co...@chrismaloney.com> wrote:
> I'd like to hear feedback if there are any drawbacks to my approach to
> this, which is to break *all* of my pipelines into one-transformer
> chunks, and use the cocoon:/ protocol to tie them together. That way, I
> can look at the output of any stage by just typing in a URL.
>
> For example, here's a typical bit of my sitemap:
> <map:match pattern='**.InclArrows.xml'>
> <map:generate src="cocoon:/{1}.0A.xml"/>
> <map:transform src="SS/Level0A-to-InclArrows.xslt"/>
> <map:serialize type="xml"/>
> </map:match>
>
> <map:match pattern='**.WithArrows.xml'>
> <map:generate src="cocoon:/{1}.InclArrows.xml"/>
> <map:transform type='cinclude'/>
> <map:serialize type="xml"/>
> </map:match>
>
> <map:match pattern='**.Slides.html'>
> <map:generate src='cocoon:/{1}.WithArrows.xml'/>
> <map:transform src='SS/WithArrows-to-Slides.xslt'/>
> <map:serialize type='xhtml'/>
> </map:match>
>
> The bit of extra work involved is coming up with a name for each output.
>
> Is this significantly slower than chaining all the transformers
> together? Do you think, would it be slower than using the FotoTransformer?
>
> Chris
>
>
> Adam Walsh wrote:
>
> > This might be the kind of thing that you're looking for:
> >
> > http://wiki.apache.org/cocoon/FotoTransformer
> >
> > HTH,
> > Adam
> >
> > Irv Salisbury wrote:
> >
> >> In a pipeline we have for producing XML data for our forms, we'd like
> >> to be able to debug what is happening at various points in the
> >> pipeline. We can't use the cocoon-view stuff, as we can't call this
> >> URL directly, and it needs a number of things setup to produce the
> >> form, etc. I see there is a LogTransformer which is "close" to what I
> >> need, except it produces somewhat cryptic output based on SAXEvents.
> >>
> >> Has anyone written a LogTransformer like thing that dumps regular XML
> >> output to a file?
> >>
> >> Or, has anyone any other ideas on debugging these very "internal"
> >> pipelines that can't be done with cocoon-view?
> >>
> >> Thanks,
> >>
> >> Irv
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
> >> For additional commands, e-mail: users-help@cocoon.apache.org
> >>
> >>
> >>
> >>
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
> > For additional commands, e-mail: users-help@cocoon.apache.org
> >
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
> For additional commands, e-mail: users-help@cocoon.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: Log transformer, logging pipelines
Posted by Chris Maloney <co...@chrismaloney.com>.
I'd like to hear feedback if there are any drawbacks to my approach to
this, which is to break *all* of my pipelines into one-transformer
chunks, and use the cocoon:/ protocol to tie them together. That way, I
can look at the output of any stage by just typing in a URL.
For example, here's a typical bit of my sitemap:
<map:match pattern='**.InclArrows.xml'>
<map:generate src="cocoon:/{1}.0A.xml"/>
<map:transform src="SS/Level0A-to-InclArrows.xslt"/>
<map:serialize type="xml"/>
</map:match>
<map:match pattern='**.WithArrows.xml'>
<map:generate src="cocoon:/{1}.InclArrows.xml"/>
<map:transform type='cinclude'/>
<map:serialize type="xml"/>
</map:match>
<map:match pattern='**.Slides.html'>
<map:generate src='cocoon:/{1}.WithArrows.xml'/>
<map:transform src='SS/WithArrows-to-Slides.xslt'/>
<map:serialize type='xhtml'/>
</map:match>
The bit of extra work involved is coming up with a name for each output.
Is this significantly slower than chaining all the transformers
together? Do you think, would it be slower than using the FotoTransformer?
Chris
Adam Walsh wrote:
> This might be the kind of thing that you're looking for:
>
> http://wiki.apache.org/cocoon/FotoTransformer
>
> HTH,
> Adam
>
> Irv Salisbury wrote:
>
>> In a pipeline we have for producing XML data for our forms, we'd like
>> to be able to debug what is happening at various points in the
>> pipeline. We can't use the cocoon-view stuff, as we can't call this
>> URL directly, and it needs a number of things setup to produce the
>> form, etc. I see there is a LogTransformer which is "close" to what I
>> need, except it produces somewhat cryptic output based on SAXEvents.
>>
>> Has anyone written a LogTransformer like thing that dumps regular XML
>> output to a file?
>>
>> Or, has anyone any other ideas on debugging these very "internal"
>> pipelines that can't be done with cocoon-view?
>>
>> Thanks,
>>
>> Irv
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
>> For additional commands, e-mail: users-help@cocoon.apache.org
>>
>>
>>
>>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
> For additional commands, e-mail: users-help@cocoon.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: Log transformer, logging pipelines
Posted by Adam Walsh <aw...@contal.net.au>.
This might be the kind of thing that you're looking for:
http://wiki.apache.org/cocoon/FotoTransformer
HTH,
Adam
Irv Salisbury wrote:
>In a pipeline we have for producing XML data for our forms, we'd like
>to be able to debug what is happening at various points in the
>pipeline. We can't use the cocoon-view stuff, as we can't call this
>URL directly, and it needs a number of things setup to produce the
>form, etc. I see there is a LogTransformer which is "close" to what I
>need, except it produces somewhat cryptic output based on SAXEvents.
>
>Has anyone written a LogTransformer like thing that dumps regular XML
>output to a file?
>
>Or, has anyone any other ideas on debugging these very "internal"
>pipelines that can't be done with cocoon-view?
>
>Thanks,
>
>Irv
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
>For additional commands, e-mail: users-help@cocoon.apache.org
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org