@@ -318,10 +318,10 @@ The service container is built using a single configuration resource
318
318
be imported from inside this file in one way or another. This gives you absolute
319
319
flexibility over the services in your application.
320
320
321
- External service configuration can be imported in two different ways. The first
322
- method, commonly used to import container configuration from the bundles you've
323
- created - is via the ``imports `` directive. The second method, although slightly more
324
- complex offers more flexibility and is commonly used to import third-party bundle
321
+ External service configuration can be imported in two different ways. The first
322
+ method, commonly used to import container configuration from the bundles you've
323
+ created - is via the ``imports `` directive. The second method, although slightly more
324
+ complex offers more flexibility and is commonly used to import third-party bundle
325
325
configuration. Read on to learn more about both methods.
326
326
327
327
.. index ::
@@ -943,13 +943,15 @@ to be used for a specific purpose. Take the following example:
943
943
xsi : schemaLocation =" http://symfony.com/schema/dic/services
944
944
http://symfony.com/schema/dic/services/services-1.0.xsd" >
945
945
946
- <service
947
- id =" foo.twig.extension"
948
- class =" Acme\HelloBundle\Extension\FooExtension"
949
- public =" false" >
946
+ <services >
947
+ <service
948
+ id =" foo.twig.extension"
949
+ class =" Acme\HelloBundle\Extension\FooExtension"
950
+ public =" false" >
950
951
951
- <tag name =" twig.extension" />
952
- </service >
952
+ <tag name =" twig.extension" />
953
+ </service >
954
+ </services >
953
955
</container >
954
956
955
957
.. code-block :: php
0 commit comments