Thorsten Scherler wrote:
org.apache.forrest.locationmap.*
I am on my way out. I do not know whether it is only accessible as an
InputModule.
Thanks, I'll take a look into that.
[...]
hmm, adding complexity? I reckon it is doing the opposite. I would
recommend to have it in the core and each pub can have their own
overriding map.
...and using existing technology is IMO better to invent lenya specific
protocols.
The last point is that our 'configuration' is hell complicated and the
locationmap seems to help solving some aspects.
I don't see how this reduces configuration complexity ...
At the moment, all you configure is the template in publication.xconf.
[...]
Another point: How would loops be implemented?
You have a chain of parents. Is it possible to use recursion?
The example has a loop.
>>> <select type="exists">
>>> <location src="pub/..." />
>>> <location src="parent/" />
>>> <location src="context://lenya/...">
>>> </select>
Does <location src="parent/" /> send another call into the location map,
i.e. does this pipeline recurse?
BTW, what I don't yet see is how this replaces the parent:// protocol?
Then please explain again what parent:// should do. Maybe I
misunderstood it.
The parent:// protocol should do the same as fallback://, but it should
skip the current publication when looking for a resource.
-- Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
