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 [EMAIL PROTECTED] Internet: http://www-uk.hpl.hp.com/people/marbut/ > -----Original Message----- > From: Carsten Ziegeler [mailto:[EMAIL PROTECTED] > 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 >
