Mailing-List: contact users-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@cocoon.apache.org
Received-SPF: pass (asf.osuosl.org: local policy)
Message-ID: <59171.199.117.205.100.1126820492.squirrel@mail.lojjic.net>
In-Reply-To: 
     <9CF7E05EDC0455439ABF5CD929818F665F075E@AK1VXCH01.tvnzad.tvnz.co.nz>
References: 
    <9CF7E05EDC0455439ABF5CD929818F665F075E@AK1VXCH01.tvnzad.tvnz.co.nz>
Date: Thu, 15 Sep 2005 15:41:32 -0600 (MDT)
Subject: RE: Request to move IncludeTransformer into next release
From: "Jason Johnston" <cocoon@lojjic.net>
To: users@cocoon.apache.org
User-Agent: SquirrelMail/1.4.4
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Importance: Normal

>
> 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 understanding your setup.  Any included source that
provides a SourceValidity will be added to the transformer's aggregated
validity, and all the pieces will be checked for validity each successive
time the pipeline is set up.

> Any indication when/if this will be committed to the cocoon src?

Nope.  But the committers generally seem pretty responsive to requests for
checkins, so if you wanted to add a comment to the bug asking for some
attention it might get the ball rolling.  I'd definitely like to see it
get committed too, though it hasn't been pressing enough thus far for me
to make a fuss.


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