You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cocoon.apache.org by Mark Lundquist <ml...@wrinkledog.com> on 2004/02/05 21:54:06 UTC
WoodyGenerator and 'attribute-name' parameter
I've got my first Woody form displaying now. I'm handling the form
request with flow that calls a display pipeline, which generates from a
Woody template and transforms with the WoodyTemplateTransformer, and
then again with woody-field-styling.xsl from the samples directory.
It works. But I'm pretty well convinced that what I really want is the
WoodyGenerator, and not to use the "pull-model" template approach. But
I'm stuck on the "attribute-name" sitemap parameter required by the
generator. Presumably this has to match up with something that my flow
is supposed to have taken care of, but I can't find any docs or
examples that explain this. Can anybody help shed some light on this
for me?
Thanks in advance for answering noob questions :-)
Best Regards,
~ml
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: WoodyGenerator and 'attribute-name' parameter
Posted by Mark Lundquist <ml...@wrinkledog.com>.
On Feb 5, 2004, at 12:54 PM, Mark Lundquist wrote:
>
> I've got my first Woody form displaying now. I'm handling the form
> request with flow that calls a display pipeline, which generates from
> a Woody template and transforms with the WoodyTemplateTransformer, and
> then again with woody-field-styling.xsl from the samples directory.
>
> It works. But I'm pretty well convinced that what I really want is
> the WoodyGenerator, and not to use the "pull-model" template approach.
> But I'm stuck on the "attribute-name" sitemap parameter required by
> the generator. Presumably this has to match up with something that my
> flow is supposed to have taken care of, but I can't find any docs or
> examples that explain this. Can anybody help shed some light on this
> for me?
With some sleuthing, I was able to figure out that I needed to call
cocoon.request.setAttribute ('foo-form', form.form);
before calling form.showForm(). Bingo, that was the ticket.
Is there anything else I should know?
Thanks,
~ml
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org