cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vadim Gritsenko" <vadim.gritse...@verizon.net>
Subject RE: [SITEMAP] Component declaration
Date Mon, 29 Apr 2002 13:34:59 GMT
> From: Konstantin Piroumian [mailto:kpiroumian@apache.org]
> 
> From: "Vadim Gritsenko" <vadim.gritsenko@verizon.net>
> > > From: Konstantin Piroumian [mailto:kpiroumian@apache.org]
> > >
> > > Hi, Cocooners!
> > >
> > > A simple question: why in a sub sitemap we need to add
<map:components
> > /> if
> > > we add anything to the list?
> >
> > From the sub sitemap:
> >   <map:generators default="file"/>
> >
> > From the sitemap.xsl:
> >       <xsl:with-param name="default-component"
> > select="/map:sitemap/map:components/map:generators/@default"/>
> >
> >
> > If you know better way how in XSLT get default component, you could
> > modify compiled sitemap engine so it does not requires
<map:components
> > /> section.
> 
> A guess:
>     <xsl:variable name="$default">
>         <xsl:choose>...check if we have declared default, set to
'file', if
> no</xsl:choose>
>     </xsl:variable>
>     ...
>        <xsl:with-param name="default-component"
>  select="{$default}"/> ?

Hardcoded? No joy... I would leave it alone unchanged (anyway, 2.0.3
branch is frozen for new features)

<snip/>

> > > Isn't it possible to inherit components implicitly?
> >
> > They are inherited. But you want to know the default.
> 
> Why I have to know it? I have to be able to change the default or
declare it
> explicitely to be sure, but if I am Ok with the inherited one then I'd
like
> to omit that part of the sitemap.

I was talking about compiled engine.

<snip/>

> > >     - what is the best place for such a template/sample
> >
> > samples directory?
> 
> Samples directory is for samples (that are rarely changed by user). I
want
> this app to be some template where a new user can start making his own
> application. Maybe just a 'myapp' in the webapp directory?

Ok


> > >     - is it worth making a special target for building a minimal
> > > Cocoon
> > > containing a very minimal set of features?
> >
> > May be better documenting the process will help. It boils down to
just
> > couple of steps:
> > 1. build clean
> 
> This means that the user has sources. What about a distribution of
just a
> cocoon-myapp.war? (Just like Struts' struts-blank.war)

Hm. Demand is high, I would say let's do this. If we add set of options
like "-Duse.batik=yes" to the build script and copy batik/compile
batik-related classes/add batik sitemap entries only if it is true, then
it will be easy to create target for "cocoon-blank.war".


Vadim


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


Mime
View raw message