What makes this case really complicated is that you have a
two-step-processing of pipeline content. It would be much easier if you
could determine the norm_id directly
Hm, thought this was, was actions are used for, among other things.
The Pipeline gets called from an HTML-Href-Link inside of an
On 23.04.2007 17:27, SETIssl wrote:
I tried to implement a DatabaseSelectAction like its described in the
docs and the api, but couldn't find any details or any kind of example
on how the request/the sitemap pipeline action part actually should look
like.
From rereading the thread I get
Thanks for your reply.
I tried to implement a DatabaseSelectAction like its described in the docs
and the api, but couldn't find any details or any kind of example on how
the request/the sitemap pipeline action part actually should look like.
so if anyone got this action type working or a
On 13.03.2007 23:35, SETIssl wrote:
All working fine till here, the transformer gets the documents norm id
from the database and puts it in the sax stream(?) in the place where
docnorm/ was before.
But now in the next step i need this norm_id value in the sitemap for
choosing the next
hello, i need some advice for my document management application based on
cocoon.
i've got an xml-file with the structure
document
docnorm/
sender/ receiver/ content/ ...
/document
Now this file gets loaded into a pipeline with the file generator and
transformed in the next step by an
