Andreas Hartmann schrieb:
> Richard Frovarp schrieb:
>> Andreas Hartmann wrote:
>
> [...]
>
>>> We wouldn't require that the module contains a
menu - the implication
>>> of the test result is that the performance
degrades if the
>>> publication.xml contains references to modules
which don't contain a
>>> menu. At least this is my interpretation, and a
debugging session
>>> indicated that this is really the case.
>>>
>>> So a possible approach to enforce a performant
configuration would be
>>> not to deliver an empty menu XML for those
modules but to throw an
>>> exception instead, so that the user is forced
to remove the
>>> "offending" module references from
publication.xml.
>>>
>>> -- Andreas
>>>
>>>
>>
>> Our documentation states that the modules need to
be listed to
>> generate the menus and to access i18n messages.
Something like
>> notification doesn't have menus, but does need
i18n. How would that work?
>
> I'm currently working on this issue. My idea is to use
a generator to
> provide a list of all available modules, and to
generate a complete i18n
> catalogue including the messages of all modules. It
would of course be
> great if this catalogue could also be cached, but I
doubt that this will
> be possible without requiring all modules to contain
i18n catalogues.
> Maybe someone has an idea how to solve this problem
...
One approach would be to override the IncludeTransformer.
The existence
of the missing sources would be checked everytime the
content is
requested, and if the sources still don't exist and the
other source
validities are still valid, the cached content is returned.
I think this
is worth a try, when I find the time I'll try to implement
this and do
some more testing.
-- Andreas
--
Andreas Hartmann, CTO
BeCompany GmbH
http://www.becompany.ch
Tel.: +41 (0) 43 818 57 01
------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribe lenya.apache.org
For additional commands, e-mail: dev-help lenya.apache.org
|