Return-Path: 
 <cocoon-dev-return-37830-apmail-xml-cocoon-dev-archive=xml.apache.org@xml.apache.org>
Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org
Received: (qmail 83965 invoked by uid 500); 6 Mar 2003 14:27:57 -0000
Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:cocoon-dev-help@xml.apache.org>
list-unsubscribe: <mailto:cocoon-dev-unsubscribe@xml.apache.org>
list-post: <mailto:cocoon-dev@xml.apache.org>
Reply-To: cocoon-dev@xml.apache.org
Delivered-To: mailing list cocoon-dev@xml.apache.org
Received: (qmail 83952 invoked from network); 6 Mar 2003 14:27:56 -0000
Received: from hplb.hpl.hp.com (192.6.10.2)
  by daedalus.apache.org with SMTP; 6 Mar 2003 14:27:56 -0000
Received: from 0-mail-1.hpl.hp.com (0-mail-1.hpl.hp.com [15.144.81.13])
	by hplb.hpl.hp.com (8.12.8/8.12.1/HP Labs Bristol relay) with SMTP id
 h26ERhvQ014246
	for <cocoon-dev@xml.apache.org>; Thu, 6 Mar 2003 14:27:45 GMT
Received: from 15.144.89.13 by 0-mail-1.hpl.hp.com (InterScan E-Mail VirusWall
 NT); Thu, 06 Mar 2003 14:27:43 -0000
Received: by 0-mail-1.hpl.hp.com with Internet Mail Service (5.5.2653.19)
	id <G1KTDZ2Y>; Thu, 6 Mar 2003 14:27:43 -0000
Message-ID: <5E13A1874524D411A876006008CD059F04501EBD@0-mail-1.hpl.hp.com>
From: "Butler, Mark" <Mark_Butler@hplb.hpl.hp.com>
To: "'cocoon-dev@xml.apache.org'" <cocoon-dev@xml.apache.org>
Subject: RE: DeliTransformer and DeliComponent
Date: Thu, 6 Mar 2003 14:27:42 -0000 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
X-MailScanner: Found to be clean
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

Hi Carsten

Simplifying sounds a good idea. 

However I have a question - apologies in advance about my ignorance of the
avalon lifecycle - if the deli component fails sometime during the
contextualize / compose / parameterize / initalize phase, does this mean the
check
 if (this.manager.hasComponent(Deli.ROLE)) 
will be false i.e. the DELI component only become available after
initialize? If so perhaps there is an argument for keeping the check in
DeliTransformer.java?

I have a question BTW - in sitemap, how do I call the DeliTransformer rather
than the TraxTransformer?

thanks, sorry about the delay in replying but I'm in Boston

Mark H. Butler, PhD
Research Scientist                HP Labs Bristol
mark-h_butler@hp.com
Internet: http://www-uk.hpl.hp.com/people/marbut/


> -----Original Message-----
> From: Carsten Ziegeler [mailto:cziegeler@s-und-n.de]
> Sent: 06 March 2003 08:30
> To: Cocoon-Dev
> Subject: DeliTransformer and DeliComponent
> 
> 
> Just a quick question: The new deli transformer in the deli block
> still tests if the deli component is available. Shouldn't we remove
> this extra test? Because either the deli block (with component and
> transformer is installed) or it is not.
> 
> What do you think?
> 
> 
> Carsten 
> 
> Carsten Ziegeler 
> Open Source Group, S&N AG
>