> From: Zack Angelo [mailto:[EMAIL PROTECTED]]
>
>
> I had a feeling that would be rather inefficient.
>
> I'm developing a web application based on a modular framework. Each
> module (a sector of the application) has its own subdirectory, with
its
> own sitemap. So, each sub-sitemap must be mounted in the primary
> sitemap. I'd like for whenever a module is inserted into the
database,
> for the sitemap to reflect those changes.
1. Module URI matches module directory
<map:match pattern="*/**">
<map:mount uri-prefix="{1}/" src="{1}/sitemap.xmap"
check-reload="yes"/>
</map:match>
2. Module URI does not match module directory
<map:match pattern="*/**">
<map:action type="get-module-dir>
<map:parameter name="uri" value="{1}"/>
<map:mount uri-prefix="{../1}" src="{1}/sitemap.xmap"
check-reload="yes"/>
</map:action>
</map:match>
Doesn't this solve the problem with static sitemap?
Vadim
> -Zack
>
>
> > -----Original Message-----
> > From: Nicola Ken Barozzi [mailto:[EMAIL PROTECTED]]
> > Sent: Tuesday, May 21, 2002 1:44 AM
> > To: [EMAIL PROTECTED]
> > Subject: Re: esql in sitemap
> >
> > From: "Zack Angelo" <[EMAIL PROTECTED]>
> >
> > > Is it possible (and/or practical) to use esql to dynamically
> generate
> > > parts of my sitemap?
> >
> > Possible, but definately a big time hack that is generally
> impractical.
> >
> > Sitemaps are meant to change very little, compared to other content;
> on
> > this
> > assumption Cooon does optimizations.
> >
> > I'm sure you can achieve your goal without having to do this: what
are
> > your
> > needs-scenario?
> > I'm curious :-?
> >
> > --
> > Nicola Ken Barozzi [EMAIL PROTECTED]
> > - verba volant, scripta manent -
> > (discussions get forgotten, just code remains)
> >
---------------------------------------------------------------------
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>
