diff options
| author | Carlos de la Guardia <cguardia@yahoo.com> | 2010-03-26 22:58:10 +0000 |
|---|---|---|
| committer | Carlos de la Guardia <cguardia@yahoo.com> | 2010-03-26 22:58:10 +0000 |
| commit | 05f19008c1d312e903a40a0b9827252541a8942e (patch) | |
| tree | 2e70a0bf18ce708685191be51442c31e070610dc /docs | |
| parent | 69364d6622e5354107b1db178fba06e9d29dda77 (diff) | |
| download | pyramid-05f19008c1d312e903a40a0b9827252541a8942e.tar.gz pyramid-05f19008c1d312e903a40a0b9827252541a8942e.tar.bz2 pyramid-05f19008c1d312e903a40a0b9827252541a8942e.zip | |
quick fixes for chapter
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/narr/extending.rst | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/docs/narr/extending.rst b/docs/narr/extending.rst index e06488470..3a9518020 100644 --- a/docs/narr/extending.rst +++ b/docs/narr/extending.rst @@ -20,12 +20,12 @@ maximally extensible :mod:`repoze.bfg` application: you should not use any :term:`configuration decoration` or :term:`imperative configuration`. This means the application developer should avoid relying on :term:`configuration decoration` meant to be detected via -the a :term:`scan`, and you mustn't configure your :mod:`repoze.bfg` +a :term:`scan`, and you mustn't configure your :mod:`repoze.bfg` application *imperatively* by using any code which configures the application through methods of the :term:`Configurator` (except for the :meth:`repoze.bfg.configuration.Configurator.load_zcml` method). -Instead, must always use :term:`ZCML` for the equivalent +Instead, you must always use :term:`ZCML` for the equivalent purposes. :term:`ZCML` declarations that belong to an application can be "overridden" by integrators as necessary, but decorators and imperative code which perform the same tasks cannot. Use only @@ -107,7 +107,7 @@ configuration imperatively, one of two things may be true: :meth:`repoze.bfg.configuration.Configurator.scan` method). This will cause the decorators to do nothing. At this point, you will need to convert all the configuration done in decorators into - equivalent :term:`ZCML` and add that ZCML to an a separate Python + equivalent :term:`ZCML` and add that ZCML to a separate Python package as described in :ref:`extending_the_application`. If the source of trouble is configuration done imperatively in a @@ -151,7 +151,7 @@ something like this: package="theoriginalapp" file="views.zcml"/>``. - On a line in the new package's ``configure.zcml`` file that falls - after (XML-ordering-wise) the all ``include`` statements of original + after (XML-ordering-wise) all the ``include`` statements of the original package ZCML, put an ``includeOverrides`` statement which identifies *another* ZCML file within the new package (for example ``<includeOverrides file="overrides.zcml"/>``. |