Thorsten Scherler wrote:
[...]
The only thing that can cause memory and performance troubles is patching
cocoon.xconf.
...and deploying the java stuff from this 1 million modules. ;)
Thanks to dynamic class loading this is only a compile-time performance
issue.
[...]
In forrest we have
project.required.plugins=org.apache.forrest.plugin.output.pdf,org.apache.forrest.plugin.internal.dispatcher,org.apache.forrest.themes.core,org.apache.forrest.plugin.output.search
This property is responsible which plugins (similar to modules) got
mounted for the certain project.
In Lenya, this is modules.root.dirs in local.build.properties.
Jaein. ;) Yes and no, but I maybe I learned something where forrest can
overcome some currently raising issues with plugins. ;)
In lenya we use the root dir (all modules got included) in forrest we
define each plugin.
That would be OK with me, I guess it would simplify the build process.
I think we should have something similar and not mount every single
module.
We do have something similar - see above.
Imagine further there are modules that are trying to do the
same. Which one will be taken and how to control it?
Modules are referenced by the module name, not by their capabilities.
So there is no confusion which module will be taken.
yes, right, for usecases no problem at all.
...but what about the matches in the sitemap from the modules? What
happends if I define two times the same match in two different modules?
Which one will be taken and how can I control it?
Hmmm, I don't quite understand ...
You call the module explicitely using its name, so why should there
be two modules which could be called?
cocoon://modules/<module-name>/...
That is why I thought that I need to declare the modules in the
publication.xconf, which makes for me perfect sense. ;)
No, we can't determine which modules to install based on publication.xconf
(see my first comment in this mail).
Yes, but actually we cannot add new publications on run-time now,
right? ;)
We can: localhost:8888/index.html -> "New publication"
-- Andreas
--
Andreas Hartmann
Wyona Inc. - Open Source Content Management - Apache Lenya
http://www.wyona.com http://lenya.apache.org
[EMAIL PROTECTED] [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
