Mailing-List: contact users-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@cocoon.apache.org
Message-ID: <40E3C656.3050706@upaya.co.uk>
Date: Thu, 01 Jul 2004 09:07:50 +0100
From: Upayavira <uv@upaya.co.uk>
User-Agent: Mozilla Thunderbird 0.7 (Windows/20040616)
MIME-Version: 1.0
To: users@cocoon.apache.org
Subject: Re: cocoon and hibernate sessions
References: <05fa01c45e55$589de370$0c01000a@jsc> <40E283EA.6020509@gmx.net>
 <40E2B0C6.1050106@upaya.co.uk> <40E328C0.9040207@gmx.net>
In-Reply-To: <40E328C0.9040207@gmx.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Stephan Coboos wrote:

> Upayavira wrote:
>
>>>
>>>
>>> <map:match pattern="foo.jxt">
>>>    <map:generate type="jxt" src="foo.jxt"/>
>>>    <map:act type="closeHibernateSession"/>
>>>    <map:serialize type="html"/>
>>> </map:match>
>>>
>> This will not work.
>>
>> Actions are used when building a pipeline, not when processing it. So 
>> the action will take place before the view is processed, not after.
>
>
>
> Oh, what a pitty. It's a little bit consfusing me why action is 
> executed before processing the pipeline, but OK it is so. I think of 
> process switch within the pipline?

Actually, when understood, it makes complete sense.

So, to explain:

Any pipeline when built, goes generator->transformer...->serializer. And 
that is it. Anything else, such as matchers, selectors and actions, that 
influence the pipeline, are used when building the pipeline, not when 
using it. So imagine a process that goes:
1) Which generator? Which transformers? Which serialiser
2) Okay, I've worked out my pipeline, so: generator, go generate

And the generator then starts up, passing SAX events down the pipeline 
until the serialiser has consumed all resulting events and something has 
been returned to the user.

Thus, actions are used when _building_ pipelines, not when _executing_ them.

Hope that makes sense.

Upayavira


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org