Quoting Carsten Ziegeler <cziegeler@sundn.de>:
> > Berin Loritsch wrote:
> > 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.
BTW: Take into account that the parser (as the only component in the system) is
*not* added because of the configuration cocoon.xconf but because Cocoon adds it
expicitly. Its because the hole configuration system needs a parser to read the
cocoon.xconf file.
Giacomo
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
|