consolidating publication config

hi *!


i wonder: should we also move the access controller and
search engine 
configuration into publication.xconf?

from a usablity POV, that would be a huge plus - users only
need to 
check one file, and all configuration would profit from the
validation 
of publication.xconf.
moreover, the current separation leads to problems with
nonstandard 
content-dir settings: the directory has to be entered
manually in all 
three files, which is error-prone and generally
undesirable.

but it requires some thought: PublicationConfiguration
should not be 
concerned with the inner workings of lucene, since it's an
external 
component. so our lucene adapter (whatever it is, haven't
investigated 
yet) should read directly from publication.xconf. possible?
the access controller config could go in publication.xconf
anyway - it's 
quite natural to consider it a property of the publication
itself.

any opinions on this?


regards,

jörn



------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribelenya.apache.org
For additional commands, e-mail: dev-helplenya.apache.org