El jue, 19-01-2006 a las 13:29 +0100, Felix Röthenbacher escribió:
>
> Thorsten Scherler wrote:
> > El jue, 19-01-2006 a las 11:29 +0100, Felix Röthenbacher escribió:
> >
> >>Thorsten Scherler wrote:
> >>
> > ...
> >
> >>>Were else the locationmap let the *user* define the location and the
> >>>"to-be-used" fallbacks:
> >>><match pattern="tabs.xml">
> >>> <select type="exists">
> >>> <location src="{project:content.xdocs}tabs1.xml"/>
> >>> <location src="{project:content.xdocs}tabs2.xml"/>
> >>> </select>
> >>></match>
> >>>
> > ...
> >
> >>Can you give an example how Lenya's templating hierarchy will look like
> >>implemented with the locationmap protocol?
> >>
> >>Thanks, Felix
> >
> >
> > I will try but no guarantee that it is correct, since I could not find
> > any documentation about fallback in our official docu (hint, hint). ;-)
> >
> > <match pattern="fallback.**">
> > <select type="exists">
> > <location src="context://{lenya:pubId}/lenya/**"/>
> > <location src="context://{lenya:pubId}/**"/>
> > <location src="context://lenya/**"/>
> > <location src="context://**"/>
> > </select>
> > </match>
>
> How do you implement a recursive dependency of publications like
>
> pubA <-- pubB <-- pubC <-- pubD
That highly depends on how we implement the locationmap in the core. The
locationmap is configured via *one* locationmap, but within this map you
can mount other locationsmap.
http://svn.apache.org/viewcvs.cgi/forrest/trunk/main/webapp/locationmap.xml?view=markup
"...
<select>
<!-- Normally it is discouraged to use the cocoon:
protocol in the locationmap as this provides too much indirection.
However, this is a special case since it allows individual
projects to dynamically generate their locationmap. This is
required when content is being drawn from a remote repository
and we want the site structure to also come from that repository
-->
<mount src="cocoon://locationmap-project.xml"/>
</select>"
Something similar we can implement for lenya, still if you want to define in
which order
the locationmap will mount the dependent pubs I reckon we need to write a
custom action
(e.g. reuse the fallback:// logic).
>
> so that a resource not found in pubD is taken from one of its parents?
See the lm action I posted a link for.
> What are the prerequesites for configuring the templating hierarchy?
>
Do not understand what you mean, can you specify?
salu2
--
thorsten
"Together we stand, divided we fall!"
Hey you (Pink Floyd)
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
