IncludeTransformer: 2 parallel threads only ?

Hello all, I am currently working with the parallel inclusion through the IncludeTransformer. Our website is based on Cocoon 2.1.11. It works fine and we truly like this feature, but I notice some strange behaviour : a.. I have a XSP page with 4 i:include inclusions. We configured

Re: IncludeTransformer: 2 parallel threads only ?

explain me why do i have this behaviour. Christophe. From: Christophe Fondacci Sent: Thursday, June 11, 2009 10:26 AM To: users@cocoon.apache.org Subject: IncludeTransformer: 2 parallel threads only ? Hello all, I am currently working with the parallel inclusion through the IncludeTransformer

Re: IncludeTransformer: 2 parallel threads only ?

); } The second external inclusion processed by the IncludeTransformer is waiting for synch on the addSource method call. When working with sitemap inclusions (cocoon://), the source.getValidity performed by the addSource method returns immediately without really invoking the URL. There is no synchronization

Cocoon 2.1 - IncludeTransformer and caching

like this method to run :) Normally when I transfrom my files with MyCustomTransformer everythings is fine, but with IncludeTransformer it does not work... Is this some kind of undocumented feature or I'm doing something wrong? Thanks Maciek

Re: IncludeTransformer

Sébastien Geindre wrote: How can i log the http header of a request made by CIcludeTransformer ? One possibility would be to use Axis' tcpmon utility (http://ws.apache.org/axis/java/user-guide.html#AppendixUsingTheAxisTCPMonitorTcpmon)? Just change the CInclude to use localhost and

Re: IncludeTransformer

Second approach : use transformer given by franco (http://www.mail-archive.com/users@cocoon.apache.org/msg39623.html), but it seems to not be compatible with C2.2. public class HTTPPostTransformer extends AbstractTransformer implements Recyclable, Composable { ... this

RE: IncludeTransformer -- it works

in lieu on the query.. Eric -Message d'origine- De : Boisvert, Eric [mailto:[EMAIL PROTECTED] Envoyé : 17 janvier 2008 10:48 À : users@cocoon.apache.org Objet : RE: IncludeTransformer -- it works I'll be damned.. It works perfectly ! Here's my pipeline map:pipeline map:match pattern=dev

Re: IncludeTransformer

I never try, but I will shortly (like.. Today) for exactly the same reasons Sébastien (to fetch data from a remote WFS). STX is a bit more tricky that XSLT but in a simple series of WFS calls, it should be quite obvious. The great benefit of STX is that it's SAX driven (so I don't expect

Re: IncludeTransformer

I see your saga with calling an external service continues It's a real saga !!! I am writing the season 2 !!! what exactly http header parameters you need to set while calling your service? i wrote a WFS transformer which take a WFS xml request and make the http post request to a WFS

IncludeTransformer

hi all, I wonder if i need to set all http header parameters when i user IncludeTransformer or CIncludeTransformer requesting an external xml ressrouce via http post any idea ? thanks. -- Sébastien Geindre DPREVI/AERO/DEV sebastien.geindre __at__ meteo.fr

Re: Request to move IncludeTransformer into next release

of its included content. CInclude only provides expiry/time-based validity - the included content's validity is ignored. XInclude isn't Cacheable. IncludeTransformer enables us to tweak our caching very finely for content coming from our database - updates to the database trigger a cache clear

Request to move IncludeTransformer into next release

nored.XInclude isn't Cacheable. IncludeTransformerenables us to tweak our caching very finely for content coming from our database - updates to the database trigger a cache clear event on the Cocoon server. With the scratchpad IncludeTransformer _any_ pipeline thatincludes that dataat any po

Re: Request to move IncludeTransformer into next release

We use the org.apache.cocoon.transformation.IncludeTransformer class from the scratchpad block in Cocoon 2.1.6. We've just looked closely at 2.1.7 and discovered that the scratchpad block is not part of the release. ... - it provides critical (for us) cache functionality not provided by

RE: Request to move IncludeTransformer into next release

/if this will be committed to the cocoon src? Cheers, Ollie -Original Message- From: Jason Johnston [mailto:[EMAIL PROTECTED] Sent: Friday, 16 September 2005 9:12 a.m. To: users@cocoon.apache.org Subject: Re: Request to move IncludeTransformer into next release We use

RE: Request to move IncludeTransformer into next release

Thanks Jason, it would be nice to use a standard-compliant include component. We'll look into it. All we really need is for it to include the EventValidity we place on our initial data generator step. From the comments in bugzilla, it looks like your patch will do this. Yes it should, if I'm

RE: Request to move IncludeTransformer into next release

IncludeTransformer into next release Thanks Jason, it would be nice to use a standard-compliant include component. We'll look into it. All we really need is for it to include the EventValidity we place on our initial data generator step. From the comments in bugzilla, it looks like your patch

Re: Request to move IncludeTransformer into next release

Oliver Powell wrote: Another question about the cacheable XIncludeTransformer. I assume the Xpath parameter is used to form the cache key? Actually, no, but it shouldn't matter... the thinking is that if the source file as a whole is valid then any fragments within it will also be valid.

RE: Request to move IncludeTransformer into next release

: Request to move IncludeTransformer into next release Oliver Powell wrote: Another question about the cacheable XIncludeTransformer. I assume the Xpath parameter is used to form the cache key? Actually, no, but it shouldn't matter... the thinking is that if the source file as a whole is valid