Return-Path: 
 <cocoon-dev-return-21906-apmail-xml-cocoon-dev-archive=xml.apache.org@xml.apache.org>
Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org
Received: (qmail 96994 invoked by uid 500); 30 Jan 2002 14:54:02 -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 96921 invoked from network); 30 Jan 2002 14:54:02 -0000
Message-ID: <5E13A1874524D411A876006008CD059F031A1463@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: Plans for upcoming release: DELI
Date: Wed, 30 Jan 2002 14:54:00 -0000
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

Configuring DELI & TraxTransformer:

1. Sitemap.xmap

Yes it is much better to turn DELI on locally in a <map:match> block in
sitemap.xmap using

<map:parameter name="use-deli" value="true"/>

Thanks (Carsten + Michael?). This seems a better solution the turning DELI
on globally in the <map:Transformer name="xslt" block. 

Please can someone update sitemap.xmap to remove the <use-deli> statement in
<map:Transformer name="xslt" e.g.

<map:transformer name="xslt"            logger="sitemap.transformer.xslt"
                 src="org.apache.cocoon.transformation.TraxTransformer"
                 pool-max="32" pool-min="16" pool-grow="4">
   <use-request-parameters>false</use-request-parameters>
   <use-browser-capabilities-db>false</use-browser-capabilities-db>
</map:transformer>

2. TraxTransformer itself

We still haven't resolved the problem with this code in TraxTransformer:

        // FIXME (VG): Replace try with hasComponent() check when it works
as expected
        //System.out.println(Deli.ROLE + ": " +
this.manager.hasComponent(Deli.ROLE));
        //if (this.manager.hasComponent(Deli.ROLE)) {
        try {
            if (this.getLogger().isDebugEnabled()) {
                getLogger().debug("Looking up " + Deli.ROLE);
            }
            this.deli = (Deli) this.manager.lookup(Deli.ROLE);
        } catch (ComponentException e) {
            getLogger().debug("Deli is not available");
        } catch (NoClassDefFoundError e) {
            getLogger().debug("Deli is not available");
        }
	//}

I wondered if it was because I had omitted the class attribute in the .xconf
e.g. 

  <deli>
    <parameter name="deli-config-file"
value="resources/deli/config/deliConfig.xml"/>
    <parameter name="use-deli" value="true"/>
  </deli>

not

  <deli class="org.apache.cocoon.components.deli.DeliImpl">
    <parameter name="deli-config-file"
value="resources/deli/config/deliConfig.xml"/>
    <parameter name="use-deli" value="true"/>
  </deli>

however including the class attribute doesn't seem to make any difference.

So questions:
- Does this class attribute need to be there?
- Anybody got any other ideas on what is causing this problem?

thanks - I get on with updating the docs now.

Mark


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