Torsten Curdt wrote: > > <snip/> > > > > Specifing the dependencies inside as sitemap parameter by > hand sucks... > > > ..although it is a possible sollution ;) > > > > > > When the transformer could get the Validities of the previous pipeline > > > components (or at least the last one) this should be > sufficient I guess. > > > > > > Carsten, or others... any idea how to obtain this information? > > > ...I am not sure if this possible at all... > > > > > Ok, I'm trying to be very wise today: ;) > > > > <turning on wise mode> > > > > It is not possible and not allowed because SoC > > > > <turning off wise mode> > > *sigh* somehow I knew you would say that ;) > > > Now, of course, I'm interested on why you need this information? > > Well, the transformer collects and stores some information that has a > different validity than the pipeline data. > > Let's assume a transformer that inserts data. So this means it's validity > depends on.... > > Transformer Output Validity depends on: > 1) > a) the validity of the previous pipeline components > b) the validity of the data that get's inserted by the transformer > > Now the transformer also gathers information that only comes from the > pipeline. So the validity of this information only depends on the validity > of the previous pipeline components. > > > Gathered Information Validity: > 2) > a) the validity of the previous pipeline components > > What I am trying to achieve is not to change the gathered information when > 2b) changes but only when 1a) = 2a) changes. > Hmm, somehow I don't get this. If the validity of the generator does not change, the same is generated by the generator. If the validity changes, the transformer is never asked as the whole pipeline is processed then.
> > I could imagine writing one pipeline components (stream and event > > pipeline) which handles this. > > Could you please elaborate a bit more? > Currently, you can configure the stream-pipeline and the event-pipeline component as either the Caching... and the NonCaching... You could implement your own CachingAndForwardValidity... Pipelines and configure them in the cocoon.xconf. Inside the implementation you could collect the validity objects and pass them on to the next step in the pipeline, so the validity of the generator can be passed on, let's say as part of the object model or something like that to the transformer and so on. As you can see by this, it is rather a controlled hack... Carsten > Thanks > -- > Torsten > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, email: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
