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="">
<map:transform type="ldap" />
<map:serialize />
</map:match>
<map:match pattern="datos/directorio/lista-personas-2">
<map:generate src="">
<map:transform type="ldap" />
<map:transform src="" />
<map:serialize />
</map:match>
</map:pipeline>
<map:pipeline type="noncaching">
<map:match pattern="datos/directorio/lista-personas">
<map:aggregate element="listas">
<map:part src="" />
<map:part src="" />
</map:aggregate>
<map:serialize />
</map:match>
</map:pipeline>
Thanks in advance.
--
Antonio
