Sidnei da Silva wrote:

> Right, seems that's my only choice for the time being.

We currently do this in our 'start Z3' script before any of the Zope imports
are done:

# Disgusting hack to use our extended config file schema rather than the
# Z3 one. TODO: Add command line options or other to Z3 to enable
# overriding this -- StuartBishop 20050406
from zdaemon.zdoptions import ZDOptions
ZDOptions.schemafile = the_path_to_our_schema_dot_xml

You can then write a schema.xml that inherits from the Z3 one:

<schema extends="../../zope/app/server/schema.xml">
  <sectiontype name="foo">
     <key name="bar" datatype="string" default="Fnord" />

  <multisection name="+" type="foo" attribute="foo" />

We are trying to centralize all our knobs and buttons into one place - ZCML
isn't suitable for tweaking an application being rolled out to multiple
servers (dev boxes, staging servers, production server instances) because
there is too much boilerplate and syntax around the knob you need to tweak,
and way too complex for a drunk sysadmin to handle. eg. it is much easier to
have 'smtp on' in launchpad.conf than it is to configure the correct IMailer
directives and whatnot with he correct magic names so that the application
sends email via SMTP rather than sendmail.

So far, ZConfig has been way overkill for this but allows us to keep our
config in the same config as the port numbers and logfile destinations
(without having to generate it from some other source, which we will
probably do in the future to solve some production rollout issues).

Stuart Bishop <[EMAIL PROTECTED]>

Attachment: signature.asc
Description: OpenPGP digital signature

Zope-Dev maillist  -
**  No cross posts or HTML encoding!  **
(Related lists - )

Reply via email to