Thorsten Scherler wrote:
[...]
should become
<map:read src="{lm:resources/shared/css/{3}.css}"
How would that be used from Java classes?
Like I would use sourceResolver.resolveURI("fallback://..."),
is there a Java API for LocationMaps, or is it accessible as an
InputModule only?
mime-type="text/css" />
Then you can have in your locationmap:
<match pattern="resources/**.css" type="request">
<select type="exists">
<location src="pub/..." />
<location src="parent/" />
<location src="context://lenya/...">
</select>
<location src="fallback://resources..." />
</match>
This way each pub can define their own fallback mechanism *without* inventing
new protocols all the time.
IMO that's just another configuration of the publication template.
A benefit is that we would use existing technology to implement
fallback, but it adds complexity to the configuration.
But there is a major problem:
Publication templating is an abstract concept which is an integral
part of Lenya. The fallback mechanism for files is just one aspect.
We need a central configuration point for a template (which cannot
be a location map), otherwise we'll run into trouble.
Another point: How would loops be implemented?
You have a chain of parents. Is it possible to use recursion?
----
BTW, what I don't yet see is how this replaces the parent:// protocol?
Thanks for the example,
-- Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
