.. index:: single: DependencyInjection; Factories
Symfony's Service Container provides a powerful way of controlling the creation of objects, allowing you to specify arguments passed to the constructor as well as calling methods and setting parameters. Sometimes, however, this will not provide you with everything you need to construct your objects. For this situation, you can use a factory to create the object and tell the service container to call a method on the factory rather than directly instantiating the class.
Suppose you have a factory that configures and returns a new NewsletterManager
object by calling the static createNewsletterManager() method:
class NewsletterManagerStaticFactory
{
public static function createNewsletterManager()
{
$newsletterManager = new NewsletterManager();
// ...
return $newsletterManager;
}
}
To make the NewsletterManager object available as a service, you can
configure the service container to use the
NewsletterManagerStaticFactory::createNewsletterManager() factory method:
.. configuration-block::
.. code-block:: yaml
# config/services.yaml
services:
# ...
App\Email\NewsletterManager:
# call the static method
factory: ['App\Email\NewsletterManagerStaticFactory', createNewsletterManager]
.. code-block:: xml
<!-- config/services.xml -->
<?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
https://symfony.com/schema/dic/services/services-1.0.xsd">
<services>
<service id="App\Email\NewsletterManager">
<!-- call the static method -->
<factory class="App\Email\NewsletterManagerStaticFactory" method="createNewsletterManager"/>
<!-- if the factory class is the same as the service class, you can omit
the 'class' attribute and define just the 'method' attribute:
<factory method="createNewsletterManager"/>
-->
</service>
</services>
</container>
.. code-block:: php
// config/services.php
use App\Email\NewsletterManager;
use App\Email\NewsletterManagerStaticFactory;
// ...
$container->register(NewsletterManager::class)
// call the static method
->setFactory([NewsletterManagerStaticFactory::class, 'createNewsletterManager']);
Note
When using a factory to create services, the value chosen for class has no effect on the resulting service. The actual class name only depends on the object that is returned by the factory. However, the configured class name may be used by compiler passes and therefore should be set to a sensible value.
If your factory is not using a static function to configure and create your service, but a regular method, you can instantiate the factory itself as a service too. Later, in the ":ref:`factories-passing-arguments-factory-method`" section, you learn how you can inject arguments in this method.
Configuration of the service container then looks like this:
.. configuration-block::
.. code-block:: yaml
# config/services.yaml
services:
# ...
App\Email\NewsletterManagerFactory: ~
App\Email\NewsletterManager:
# call a method on the specified factory service
factory: 'App\Email\NewsletterManagerFactory:createNewsletterManager'
.. code-block:: xml
<!-- config/services.xml -->
<?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
https://symfony.com/schema/dic/services/services-1.0.xsd">
<services>
<service id="App\Email\NewsletterManagerFactory"/>
<service id="App\Email\NewsletterManager">
<!-- call a method on the specified factory service -->
<factory service="App\Email\NewsletterManagerFactory"
method="createNewsletterManager"
/>
</service>
</services>
</container>
.. code-block:: php
// config/services.php
use App\Email\NewsletterManager;
use App\Email\NewsletterManagerFactory;
use Symfony\Component\DependencyInjection\Reference;
// ...
$container->register(NewsletterManagerFactory::class);
$container->register(NewsletterManager::class)
// call a method on the specified factory service
->setFactory([
new Reference(NewsletterManagerFactory::class),
'createNewsletterManager',
]);
Note
The traditional configuration syntax in YAML files used an array to define the factory service and the method name:
# config/services.yaml
App\Email\NewsletterManager:
# new syntax
factory: 'App\Email\NewsletterManagerFactory:createNewsletterManager'
# old syntax
factory: ['@App\Email\NewsletterManagerFactory', createNewsletterManager]Suppose you now change your factory method to __invoke() so that your
factory service can be used as a callback:
class InvokableNewsletterManagerFactory
{
public function __invoke()
{
$newsletterManager = new NewsletterManager();
// ...
return $newsletterManager;
}
}
.. versionadded:: 4.3
Invokable factories for services were introduced in Symfony 4.3.
Services can be created and configured via invokable factories by omitting the method name, just as routes can reference :ref:`invokable controllers <controller-service-invoke>`.
.. configuration-block::
.. code-block:: yaml
# config/services.yaml
services:
# ...
App\Email\NewsletterManager:
class: App\Email\NewsletterManager
factory: '@App\Email\NewsletterManagerFactory'
.. code-block:: xml
<!-- config/services.xml -->
<?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
https://symfony.com/schema/dic/services/services-1.0.xsd">
<services>
<!-- ... -->
<service id="App\Email\NewsletterManager"
class="App\Email\NewsletterManager">
<factory service="App\Email\NewsletterManagerFactory"/>
</service>
</services>
</container>
.. code-block:: php
// config/services.php
use App\Email\NewsletterManager;
use App\Email\NewsletterManagerFactory;
use Symfony\Component\DependencyInjection\Reference;
// ...
$container->register(NewsletterManager::class, NewsletterManager::class)
->setFactory(new Reference(NewsletterManagerFactory::class));
Tip
Arguments to your factory method are :ref:`autowired <services-autowire>` if that's enabled for your service.
If you need to pass arguments to the factory method you can use the arguments
options. For example, suppose the createNewsletterManager() method in the previous
example takes the templating service as an argument:
.. configuration-block::
.. code-block:: yaml
# config/services.yaml
services:
# ...
App\Email\NewsletterManager:
factory: 'App\Email\NewsletterManagerFactory:createNewsletterManager'
arguments: ['@templating']
.. code-block:: xml
<!-- config/services.xml -->
<?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
https://symfony.com/schema/dic/services/services-1.0.xsd">
<services>
<!-- ... -->
<service id="App\Email\NewsletterManager">
<factory service="App\Email\NewsletterManagerFactory" method="createNewsletterManager"/>
<argument type="service" id="templating"/>
</service>
</services>
</container>
.. code-block:: php
// config/services.php
use App\Email\NewsletterManager;
use App\Email\NewsletterManagerFactory;
use Symfony\Component\DependencyInjection\Reference;
// ...
$container->register(NewsletterManager::class)
->addArgument(new Reference('templating'))
->setFactory([
new Reference(NewsletterManagerFactory::class),
'createNewsletterManager',
]);