[Zope3-checkins] SVN: Zope3/trunk/src/zope/app/appsetup/schema/ put schema.xml into subfolder, so we can reference it as svn:external, see schema/README.txt

[Bernd Dorn]

Log message for revision 73861:
  put schema.xml into subfolder, so we can reference it as svn:external, see schema/README.txt

Changed:
  A   Zope3/trunk/src/zope/app/appsetup/schema/
  A   Zope3/trunk/src/zope/app/appsetup/schema/README.txt
  A   Zope3/trunk/src/zope/app/appsetup/schema/schema.xml

-=-
Added: Zope3/trunk/src/zope/app/appsetup/schema/README.txt
===================================================================
--- Zope3/trunk/src/zope/app/appsetup/schema/README.txt	2007-03-28 14:28:27 UTC (rev 73860)
+++ Zope3/trunk/src/zope/app/appsetup/schema/README.txt	2007-03-28 14:42:03 UTC (rev 73861)
@@ -0,0 +1,9 @@
+====================================
+Schema directory for ZConfig schemas
+====================================
+
+In order to use the schema.xml file as a base for other schemas it has
+to be accessible via a relative url. This will not work if we have an
+egg based package. So for any package that is released as an egg we
+add an svn:external to this location to reference the file.
+


Property changes on: Zope3/trunk/src/zope/app/appsetup/schema/README.txt
___________________________________________________________________
Name: svn:eol-style
   + native

Added: Zope3/trunk/src/zope/app/appsetup/schema/schema.xml
===================================================================
--- Zope3/trunk/src/zope/app/appsetup/schema/schema.xml	2007-03-28 14:28:27 UTC (rev 73860)
+++ Zope3/trunk/src/zope/app/appsetup/schema/schema.xml	2007-03-28 14:42:03 UTC (rev 73861)
@@ -0,0 +1,117 @@
+<schema>
+  <description>
+    Zope 3 Application Server configuration schema.
+
+    This schema describes the configuration options available to a
+    site administrator via the zope.conf configuration file for the Zope
+    application server.
+  </description>
+
+  <!-- database and storage types -->
+  <import package="ZODB" />
+
+  <!-- logging configuration -->
+  <import package="ZConfig.components.logger" />
+
+  <abstracttype name="zope.product.base">
+    <!-- Poor name inherited from Zope 2.
+         This can't be changed since components refer to this in a
+         similar way as to public base classes.  Components that want
+         to work with both Zope 2 and Zope 3 need this to match the
+         existing Zope 2 name.
+         -->
+    <description>
+      Base type for component-specific configuration sections.
+
+      Specific products should implement configuration sections by
+      defining sections types that implement this abstract type and
+      using their own schema component to define meaningful settings.
+
+    </description>
+  </abstracttype>
+
+  <sectiontype name="product-config" implements="zope.product.base">
+    <description>
+    Component-specific configuration, expressed as arbitrary name-value pairs.
+    </description>
+
+    <key name="+"
+         attribute="mapping"
+         required="no"
+         />
+  </sectiontype>
+
+  <multisection type="zope.product.base" name="+"
+                attribute="product_config">
+    <description>
+      Component-specific configuration stanzas.
+
+      Products may use the &lt;product-config&gt; section type, or may supply
+      a component.xml which defines section types with their own schemas.
+
+      All sections for this multisection will be collected together into the
+      'product_config' attribute of the configuration object.
+    </description>
+  </multisection>
+
+  <multisection type="ZODB.database" name="*" required="yes"
+           attribute="databases">
+    <description>
+
+      Application database.
+
+      At least one database must be specified.  The first will be used
+      as the main database.  At most one of the databases can be unnamed.
+
+      All of the databases specified will be part of a multi-database.
+      See the ZODB documentation of multi-databases for details of how
+      this is useful.
+
+    </description>
+  </multisection>
+
+  <section type="eventlog" attribute="eventlog" name="*" required="yes">
+    <description>
+      Configuration for the eventlog.
+    </description>
+  </section>
+  
+  <multisection type="logger" attribute="loggers" name="*" required="no">
+    <description>
+      Additional loggers for specific subsystems
+    </description>
+  </multisection>
+
+  <key name="site-definition" default="site.zcml">
+    <description>
+      The name of the top-level ZCML file that defines the component
+      configuration used for this site.
+    </description>
+  </key>
+
+  <multikey name="path" datatype="string">
+    <description>
+      This specifies additional paths directories which are inserted into
+      the beginning of Python's module search path.  The set of directories
+      specified is inserted into the beginning of the module search path in
+      the order which they are specified here.  Note that the processing of
+      this directive may happen too late under some circumstances; it is
+      recommended that you use the PYTHONPATH environment variable if
+      using this directive doesn't work for you.
+    </description>
+    <metadefault>$softwarehome/src</metadefault>
+  </multikey>
+
+  <key name="devmode" datatype="boolean" default="off">
+    <description>
+      Switches the Developer Mode on and off.
+
+      In developer mode, the web UI will provide useful utilities for
+      developers to work on Zope 3 applications.
+    </description>
+    <example>
+      devmode on
+    </example>
+    <metadefault>off</metadefault>
+  </key>
+</schema>


Property changes on: Zope3/trunk/src/zope/app/appsetup/schema/schema.xml
___________________________________________________________________
Name: svn:eol-style
   + native