On 1/24/06, Andreas Hartmann <[EMAIL PROTECTED]> wrote:
> Thorsten Scherler wrote:
> > We need a central interface that is responsible to look up and manage
> > assets. The storage of this assets would be ideally a combination of
> > decentralized, so modules can easily register resources in this asset
> > storage, and centralized for publications.
>
> I guess everybody agrees that we need a centralized asset management,
> but IIUC this thread is about another issue.
>
> If you provide an application like BXE, Kupu, or FCK as a module, you're
> confronted with a large amount of resources of different kinds. You
> don't want to import the resources as Lenya assets. This would just be
> overkill and require a lot of maintenance work when you're e.g. updating
> to a newer version of the application.
>
> I like Simon's suggestion. At a first glance, I'd think it would be
> sufficient to deliver module resources directly from a core sitemap,
> but mounting the module sitemap is more flexible. Maybe we could
> implement both:
> <map:match pattern="modules/*/**">
> <map:select type="resource-exists">
>
> <!-- resource exists - serve statically -->
> <map:when test="lenya/modules/{1}/resources/{2}">
> <map:mount src="module-resources.xmap"/>
> </map:when>
>
> <!-- resource doesn't exist - delegate to module -->
> <map:otherwise>
> <map:mount src="modules/{1}/sitemap.xmap"/>
> </map:otherwise>
>
> </map:select>
> </map:match>
I thought that was the purpose of fallback. Any resource (or any
other type of file) uses the local (Module-specific) resource if it
exists, otherwise Lenya automatically searches the parent modules,
then global resources until it finds it.
solprovider
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
