Update of /var/cvs/config
In directory james.mmbase.org:/tmp/cvs-serv28354
Modified Files:
README
Log Message:
some explanation about new features
See also: http://cvs.mmbase.org/viewcvs/config
Index: README
===================================================================
RCS file: /var/cvs/config/README,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- README 18 Dec 2005 09:07:53 -0000 1.1
+++ README 12 Sep 2008 06:06:10 -0000 1.2
@@ -6,10 +6,16 @@
Configuration can be on multiple locations in MMBase. Every file found here,
could also be found as
a 'resource' in (in order of descending prevalence):
+
+- The location of any resource can be explicitely overriden with an
application context setting like
+ this (in the server.xml of tomcat):
+ <Environment name="mmbase-config/utils/multicast.xml"
value="file://${catalina.base}/conf/multicast/nomulticast.xml"
type="java.lang.String" />
+
- A node of the type 'resources' (if installed, and of course not valid for
resources like modules/jdbc.xml,
buiders/core/object.xml , builders/resources.xml etc..)
This 'resources' builder is not widely used, new in 1.8, and should be
considered an experimental feature.
+
- Some other directory specified by the servlet context init parameter
'mmbase.config' (in web.xml) or
by a System property 'mmbase.config' (typically by the command line switch
-Dmmbase.config=..)
@@ -33,13 +39,26 @@
There can e.g. be only one modules/jdbc.xml in use.
This is valid for resources in applications, builders, dtd, log, modules,
security, util, xmlns,
xslt.
- Some of these are all 'lists of resources', with no one typical name. Since
listing cannot be done by
- class loader, in jar files one may create a list of resource names in a
resource with the name
- INDEX:
+
+ Sometimes, a resource with the same name can exist multiple times with the
same 'prevalence',
+ e.g. the same builder xml can occur in different jars. In the case of
builder xmls the one with
+ the highest version is then used (the 'version' attribution on the builder
tag in the resource
+ itself). In most other cases more or less a random one will be used, it
probably is better to not
+ depend on that, and make sure that the resource are equal, or that it does
not happen.
+
+ Most resources have a well defined name. E.g. the logging configuration is
in config/log/log.xml,
+ and log4j can be configured in the resource mentioned in _that_ resource
(default
+ config/log/log4j.xml).
+
+ Some things are read as a 'lists of resources', where the individual
resources are not known
+ beforehand in the code. These are applications, builders and modules.
MMBase will try to use
+ _all_ resources in those directories. Since listing cannot be done by a
class loader, in jar files
+ one may create a list of resource names in a resource with the name INDEX:
applications/INDEX
builders/INDEX
modules/INDEX
- (so these INDEX'es are treated like in (2).
+ (so these INDEX'es are treated like in (2)).
+
2. All representations are somehow used. Typical examples are 'datatypes.xml'
and 'caches.xml'. If
more then one of those are found, then they are all read and used.
@@ -144,4 +163,4 @@
~/mmbase/head/build$
---------------------
-Version of this file: $Id: README,v 1.1 2005/12/18 09:07:53 michiel Exp $
+Version of this file: $Id: README,v 1.2 2008/09/12 06:06:10 michiel Exp $
_______________________________________________
Cvs mailing list
[email protected]
http://lists.mmbase.org/mailman/listinfo/cvs
