How to Decorate Services
Edit this pageWarning: You are browsing the documentation for Symfony 3.0, which is no longer maintained.
Read the updated version of this page for Symfony 6.3 (the current stable version).
How to Decorate Services
When overriding an existing definition (e.g. when applying the Decorator pattern), the original service is lost:
1 2 3 4 5 6 7 8
services:
app.mailer:
class: AppBundle\Mailer
# this replaces the old app.mailer definition with the new one, the
# old definition is lost
app.mailer:
class AppBundle\DecoratingMailer
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
<?xml version="1.0" encoding="UTF-8" ?>
<container xmlns="http://symfony.com/schema/dic/services"
xmlns:xsd="http://www.w3.org/2001/XMLSchema-instance"
xsd:schemaLocation="http://symfony.com/schema/dic/services http://symfony.com/schema/dic/services/services-1.0.xsd"
>
<services>
<service id="app.mailer" class="AppBundle\Mailer" />
<!-- this replaces the old app.mailer definition with the new
one, the old definition is lost -->
<service id="app.mailer" class="AppBundle\DecoratingMailer" />
</service>
</container>
1 2 3 4 5
$container->register('app.mailer', 'AppBundle\Mailer');
// this replaces the old app.mailer definition with the new one, the
// old definition is lost
$container->register('app.mailer', 'AppBundle\DecoratingMailer');
Most of the time, that's exactly what you want to do. But sometimes,
you might want to decorate the old one instead. In this case, the
old service should be kept around to be able to reference it in the
new one. This configuration replaces app.mailer
with a new one, but keeps
a reference of the old one as app.decorating_mailer.inner
:
1 2 3 4 5 6 7 8
services:
# ...
app.decorating_mailer:
class: AppBundle\DecoratingMailer
decorates: app.mailer
arguments: ['@app.decorating_mailer.inner']
public: false
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18
<?xml version="1.0" encoding="UTF-8" ?>
<container xmlns="http://symfony.com/schema/dic/services"
xmlns:xsd="http://www.w3.org/2001/XMLSchema-instance"
xsd:schemaLocation="http://symfony.com/schema/dic/services http://symfony.com/schema/dic/services/services-1.0.xsd"
>
<services>
<!-- ... -->
<service id="app.decorating_mailer"
class="AppBundle\DecoratingMailer"
decorates="app.mailer"
public="false"
>
<argument type="service" id="app.decorating_mailer.inner" />
</service>
</service>
</container>
1 2 3 4 5 6 7 8
use Symfony\Component\DependencyInjection\Reference;
// ...
$container->register('app.decorating_mailer', 'AppBundle\DecoratingMailer')
->setDecoratedService('app.mailer')
->addArgument(new Reference('app.decorating_mailer.inner'))
->setPublic(false)
;
Here is what's going on here: the decorates
option tells the container that
the app.decorating_mailer
service replaces the app.mailer
service. By
convention, the old app.mailer
service is renamed to
app.decorating_mailer.inner
, so you can inject it into your new service.
Tip
Most of the time, the decorator should be declared private, as you will not
need to retrieve it as app.decorating_mailer
from the container.
The visibility of the decorated app.mailer
service (which is an alias
for the new service) will still be the same as the original app.mailer
visibility.
Note
The generated inner id is based on the id of the decorator service
(app.decorating_mailer
here), not of the decorated service (app.mailer
here). This is mandatory to allow several decorators on the same service
(they need to have different generated inner ids).
You can change the inner service name if you want to using the
decoration_inner_name
option:
1 2 3 4 5
services:
app.mailer:
# ...
decoration_inner_name: app.decorating_mailer.wooz
arguments: ['@app.decorating_mailer.wooz']
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
<?xml version="1.0" encoding="UTF-8" ?>
<container xmlns="http://symfony.com/schema/dic/services"
xmlns:xsd="http://www.w3.org/2001/XMLSchema-instance"
xsd:schemaLocation="http://symfony.com/schema/dic/services http://symfony.com/schema/dic/services/services-1.0.xsd"
>
<services>
<!-- ... -->
<service
decoration-inner-name="app.decorating_mailer.wooz"
>
<argument type="service" id="app.decorating_mailer.wooz" />
</service>
</service>
</container>
1 2 3 4 5 6 7
use Symfony\Component\DependencyInjection\Reference;
$container->register('app.decorating_mailer', 'AppBundle\DeocratingMailer')
->setDecoratedService('foo', 'app.decorating_mailer.wooz')
->addArgument(new Reference('app.decorating_mailer.wooz'))
// ...
;
Decoration Priority
If you want to apply more than one decorator to a service, you can control their order by configuring the priority of decoration, this can be any integer number (decorators with higher priorities will be applied first).
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
foo:
class: Foo
bar:
class: Bar
public: false
decorates: foo
decoration_priority: 5
arguments: ['@bar.inner']
baz:
class: Baz
public: false
decorates: foo
decoration_priority: 1
arguments: ['@baz.inner']
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18
<?xml version="1.0" encoding="UTF-8" ?>
<container xmlns="http://symfony.com/schema/dic/services"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://symfony.com/schema/dic/services http://symfony.com/schema/dic/services/services-1.0.xsd">
<services>
<service id="foo" class="Foo" />
<service id="bar" class="Bar" decorates="foo" decoration-priority="5" public="false">
<argument type="service" id="bar.inner" />
</service>
<service id="baz" class="Baz" decorates="foo" decoration-priority="1" public="false">
<argument type="service" id="baz.inner" />
</service>
</services>
</container>
1 2 3 4 5 6 7 8 9 10 11 12 13
use Symfony\Component\DependencyInjection\Reference;
$container->register('foo', 'Foo')
$container->register('bar', 'Bar')
->addArgument(new Reference('bar.inner'))
->setPublic(false)
->setDecoratedService('foo', null, 5);
$container->register('baz', 'Baz')
->addArgument(new Reference('baz.inner'))
->setPublic(false)
->setDecoratedService('foo', null, 1);
The generated code will be the following:
1
$this->services['foo'] = new Baz(new Bar(new Foo())));