cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Antonio Fiol Bonnín <antonio.f...@gmail.com>
Subject Fwd: LDAP transformer / Content aggregation / Cacheability
Date Mon, 18 Jul 2005 06:19:51 GMT
Reason for posting to dev@:

- Possible existence of a bug (although I hope it is a user error and you 
can help me solve it)

Yours,

-- 
Antonio

---------- Forwarded message ----------
From: Antonio Fiol Bonnín <antonio.fiol@gmail.com>
Date: 11-jul-2005 14:16
Subject: LDAP transformer / Content aggregation / Cacheability
To: users@cocoon.apache.org

Hello,

I am using the LDAP transformer, which, AFAIK, is not cacheable. However, I 
use the result of it, after a XSLT transformation, in a part of an 
aggregate. See the sitemap fragment below for details.

I am observing a strange result: if the aggregate is in a type="caching" 
pipeline, the result of the LDAP transform is cached.

Can anyone please confirm the behaviour, the reason for it and/or the 
existence of a bug?

<map:pipeline type="caching">
<map:match pattern="datos/directorio/lista-personas-1">
<map:generate src="xml/ldap/query-lista-personas-1.xml"/>
<map:transform type="ldap" />
<map:serialize />
</map:match>
<map:match pattern="datos/directorio/lista-personas-2">
<map:generate src="xml/ldap/query-lista-personas-2.xml"/>
<map:transform type="ldap" />
<map:transform src="xsl/transform-second-ldap-result.xsl" />
<map:serialize />
</map:match>
</map:pipeline>
<map:pipeline type="noncaching">
<map:match pattern="datos/directorio/lista-personas">
<map:aggregate element="listas">
<map:part src="cocoon:/datos/directorio/lista-personas-1" />
<map:part src="cocoon:/datos/directorio/lista-personas-2" />
</map:aggregate>
<map:serialize />
</map:match>
</map:pipeline>

Thanks in advance.


-- 
Antonio

Mime
View raw message