Return-Path: 
 <cocoon-dev-return-12272-apmail-xml-cocoon-dev-archive=xml.apache.org@xml.apache.org>
Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org
Received: (qmail 57010 invoked by uid 500); 10 Apr 2001 14:00:30 -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 56908 invoked from network); 10 Apr 2001 14:00:28 -0000
Message-ID: <3AD31178.61D7CD56@apache.org>
Date: Tue, 10 Apr 2001 09:58:16 -0400
From: Berin Loritsch <bloritsch@apache.org>
X-Mailer: Mozilla 4.75 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: cocoon-dev@xml.apache.org
Subject: Re: [C2]: Avalon Component Configuration
References: <NEBBLPMLKKCJBKEOKNFHMEGJDPAA.cziegeler@sundn.de>
 <986894586.3ad2d0faca205@mail.otego.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N

Giacomo Pati wrote:
> 
> Quoting Carsten Ziegeler <cziegeler@sundn.de>:
> 
> > Hi,
> >
> > I am trying to add new avalon components to the
> > cocoon.xconf (yes, for caching of course....) and am
> > now a little bit confused about the format.
> >
> > E.g. the parser has the following entries:
> >   <parser class="org.apache.cocoon.components.parser.JaxpParser"/>
> >
> >  <role name="org.apache.cocoon.components.parser.Parser"
> >        shorthand="parser"
> >        default-class="org.apache.cocoon.components.parser.JaxpParser"/>
> >
> > Is the first one obsolete? I thought the second declaration adds
> > a component with the role name "parser".
> 
> I'm not sure if the definition of the role is sufficent to define the component
> without the absolute minimum component definition (which in this case would be
> <parser/>). Berin, have you any comments on this handy?

This is possible.  You don't even need the <parser/> element at all as
long as you have a default-class mapped to a role name.  I left the <parser/>
element in the configuration file to show that it could be overridden.

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