diogo/symfony
Archived
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
This repository has been archived on 2023-08-20. You can view files and clone it, but cannot push or open issues or pull requests.
699e046b4f
symfony/src/Symfony/Bundle/FrameworkBundle/Resources/config/services.xml

58 lines
2.7 KiB
XML
Raw Normal View History

[Foundation] added the missing parts of Symfony Foundation
2010-02-17 13:54:36 +00:00
<?xml version="1.0" ?>
replaced symfony-project.org by symfony.com
2011-03-06 11:40:06 +00:00
<container xmlns="http://symfony.com/schema/dic/services"
[Foundation] added the missing parts of Symfony Foundation
2010-02-17 13:54:36 +00:00
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
replaced symfony-project.org by symfony.com
2011-03-06 11:40:06 +00:00
xsi:schemaLocation="http://symfony.com/schema/dic/services http://symfony.com/schema/dic/services/services-1.0.xsd">
[Foundation] added the missing parts of Symfony Foundation
2010-02-17 13:54:36 +00:00
fixed coding standards for XML and YAML files
2010-06-11 09:06:44 +01:00
<parameters>
Replaced EventDispatcher by Doctrine's EventManager implementation Doctrine's EventManager implementation has several advantages over the EventDispatcher implementation of Symfony2. Therefore I suggest that we use their implementation. Advantages: * Event Listeners are objects, not callbacks. These objects have handler methods that have the same name as the event. This helps a lot when reading the code and makes the code for adding an event listener shorter. * You can create Event Subscribers, which are event listeners with an additional getSubscribedEvents() method. The benefit here is that the code that registers the subscriber doesn't need to know about its implementation. * All events are defined in static Events classes, so users of IDEs benefit of code completion * The communication between the dispatching class of an event and all listeners is done through a subclass of EventArgs. This subclass can be tailored to the type of event. A constructor, setters and getters can be implemented that verify the validity of the data set into the object. See examples below. * Because each event type corresponds to an EventArgs implementation, developers of event listeners can look up the available EventArgs methods and benefit of code completion. * EventArgs::stopPropagation() is more flexible and (IMO) clearer to use than notifyUntil(). Also, it is a concept that is also used in other event implementations Before: class EventListener { public function handle(EventInterface $event, $data) { ... } } $dispatcher->connect('core.request', array($listener, 'handle')); $dispatcher->notify('core.request', new Event(...)); After (with listeners): final class Events { const onCoreRequest = 'onCoreRequest'; } class EventListener { public function onCoreRequest(RequestEventArgs $eventArgs) { ... } } $evm->addEventListener(Events::onCoreRequest, $listener); $evm->dispatchEvent(Events::onCoreRequest, new RequestEventArgs(...)); After (with subscribers): class EventSubscriber { public function onCoreRequest(RequestEventArgs $eventArgs) { ... } public function getSubscribedEvents() { return Events::onCoreRequest; } } $evm->addEventSubscriber($subscriber); $evm->dispatchEvent(Events::onCoreRequest, new RequestEventArgs(...));
2011-03-05 14:30:34 +00:00
<parameter key="event_manager.class">Symfony\Bundle\FrameworkBundle\ContainerAwareEventManager</parameter>
adds scope to the DI container
2011-01-17 22:28:59 +00:00
<parameter key="http_kernel.class">Symfony\Bundle\FrameworkBundle\HttpKernel</parameter>
removed Symfony\Framework Things have been moved to Symfony\Component\HttpKernel and Symfony\Bundle\FrameworkBundle The kernel configuration namespace was removed and merged with the main web configuration namespace (kernel:config => web:config, kernel:test => web:test, and kernel:session => web:session): Before: <kernel:config charset="UTF-8" error_handler="null" /> <web:config csrf-secret="xxxxxxxxxx"> <web:router resource="%kernel.root_dir%/config/routing.xml" /> <web:validation enabled="true" annotations="true" /> </web:config> After: <web:config csrf-secret="xxxxxxxxxx" charset="UTF-8" error-handler="null"> <web:router resource="%kernel.root_dir%/config/routing.xml" /> <web:validation enabled="true" annotations="true" /> </web:config> Renamed classes: Symfony\{Framework => Bundle\FrameworkBundle}\Cache\Cache Symfony\{Framework => Bundle\FrameworkBundle}\Client Symfony\{Framework => Bundle\FrameworkBundle}\Debug\EventDispatcher Symfony\{Framework => Bundle\FrameworkBundle}\Debug\EventDispatcherTraceableInterface Symfony\{Framework => Bundle\FrameworkBundle}\EventDispatcher Symfony\{Framework => Component\HttpFoundation}\UniversalClassLoader Symfony\{Framework => Component\HttpKernel}\Bundle\Bundle Symfony\{Framework => Component\HttpKernel}\Bundle\BundleInterface Symfony\{Framework => Component\HttpKernel}\ClassCollectionLoader Symfony\{Framework => Component\HttpKernel}\Debug\ErrorException Symfony\{Framework => Component\HttpKernel}\Debug\ErrorHandler Symfony\{Bundle\FrameworkBundle => Component\HttpKernel}\Debug\ExceptionListener Symfony\{Framework => Component\HttpKernel}\Kernel
2010-09-15 19:49:16 +01:00
<parameter key="error_handler.class">Symfony\Component\HttpKernel\Debug\ErrorHandler</parameter>
fixed coding standards for XML and YAML files
2010-06-11 09:06:44 +01:00
<parameter key="error_handler.level">null</parameter>
Fix typo
2011-01-14 14:36:00 +00:00
<parameter key="filesystem.class">Symfony\Bundle\FrameworkBundle\Util\Filesystem</parameter>
added a cache warmer sub-framework Cache warmer will come in the next commits. To warm up the cache on a production server, you can use the cache:warmup command: ./app/console_prod cache:warmup
2011-01-24 10:16:22 +00:00
<parameter key="cache_warmer.class">Symfony\Component\HttpKernel\CacheWarmer\CacheWarmerAggregate</parameter>
added an autoloader that uses a class map A class in Symfony2 can be loaded by four different mechanisms: * bootstrap.php: This file contains classes that are always required and needed very early in the request handling; * classes.php: This file contains classes that are always required and managed by extensions via addClassesToCompile(); * MapFileClassLoader: This autoloader uses a map of class/file to load classes (classes are managed by extensions via addClassesToAutoloadMap(), and should contain often used classes); * UniversalAutolaoder: This autoloader loads all other classes (it's the slowest one).
2011-01-27 13:26:49 +00:00
<parameter key="cache_warmer.autoloader_map.class">Symfony\Bundle\FrameworkBundle\CacheWarmer\ClassMapCacheWarmer</parameter>
moved common configuration classes to a new Config component
2011-02-10 15:15:51 +00:00
<parameter key="file_locator.class">Symfony\Component\HttpKernel\Config\FileLocator</parameter>
fixed coding standards for XML and YAML files
2010-06-11 09:06:44 +01:00
</parameters>
[Foundation] added the missing parts of Symfony Foundation
2010-02-17 13:54:36 +00:00
fixed coding standards for XML and YAML files
2010-06-11 09:06:44 +01:00
<services>
Replaced EventDispatcher by Doctrine's EventManager implementation Doctrine's EventManager implementation has several advantages over the EventDispatcher implementation of Symfony2. Therefore I suggest that we use their implementation. Advantages: * Event Listeners are objects, not callbacks. These objects have handler methods that have the same name as the event. This helps a lot when reading the code and makes the code for adding an event listener shorter. * You can create Event Subscribers, which are event listeners with an additional getSubscribedEvents() method. The benefit here is that the code that registers the subscriber doesn't need to know about its implementation. * All events are defined in static Events classes, so users of IDEs benefit of code completion * The communication between the dispatching class of an event and all listeners is done through a subclass of EventArgs. This subclass can be tailored to the type of event. A constructor, setters and getters can be implemented that verify the validity of the data set into the object. See examples below. * Because each event type corresponds to an EventArgs implementation, developers of event listeners can look up the available EventArgs methods and benefit of code completion. * EventArgs::stopPropagation() is more flexible and (IMO) clearer to use than notifyUntil(). Also, it is a concept that is also used in other event implementations Before: class EventListener { public function handle(EventInterface $event, $data) { ... } } $dispatcher->connect('core.request', array($listener, 'handle')); $dispatcher->notify('core.request', new Event(...)); After (with listeners): final class Events { const onCoreRequest = 'onCoreRequest'; } class EventListener { public function onCoreRequest(RequestEventArgs $eventArgs) { ... } } $evm->addEventListener(Events::onCoreRequest, $listener); $evm->dispatchEvent(Events::onCoreRequest, new RequestEventArgs(...)); After (with subscribers): class EventSubscriber { public function onCoreRequest(RequestEventArgs $eventArgs) { ... } public function getSubscribedEvents() { return Events::onCoreRequest; } } $evm->addEventSubscriber($subscriber); $evm->dispatchEvent(Events::onCoreRequest, new RequestEventArgs(...));
2011-03-05 14:30:34 +00:00
<service id="event_manager" class="%event_manager.class%">
made all event listeners lazy loaded * The register() method on all listeners has been removed * Instead, the information is now put directly in the DIC tag For instance, a listener on core.request had this method: public function register(EventDispatcher $dispatcher, $priority = 0) { $dispatcher->connect('core.response', array($this, 'filter'), $priority); } And this tag in the DIC configuration: <tag name="kernel.listener" /> Now, it only has the following configuration: <tag name="kernel.listener" event="core.response" method="filter" priority="0" /> The event and method attributes are now mandatory.
2011-01-23 17:02:16 +00:00
<argument type="service" id="service_container" />
fixed coding standards for XML and YAML files
2010-06-11 09:06:44 +01:00
</service>
[Foundation] added the missing parts of Symfony Foundation
2010-02-17 13:54:36 +00:00
DI container optimization
2011-01-05 11:13:27 +00:00
<service id="error_handler" class="%error_handler.class%" public="false">
fixed coding standards for XML and YAML files
2010-06-11 09:06:44 +01:00
<argument>%error_handler.level%</argument>
</service>
[Foundation] added the missing parts of Symfony Foundation
2010-02-17 13:54:36 +00:00
fixed coding standards for XML and YAML files
2010-06-11 09:06:44 +01:00
<service id="http_kernel" class="%http_kernel.class%">
Renamed EventArgs classes and adapted remaining code to EventManager The only missing part is ContainerAwareEventManager::addEventSubscriberService(), because I'm not sure how to find out the class name of a service in the DIC. Also, inline documentation of this code needs to be finished once it is accepted.
2011-03-07 14:42:52 +00:00
<argument type="service" id="event_manager" />
adds scope to the DI container
2011-01-17 22:28:59 +00:00
<argument type="service" id="service_container" />
changed HttpKernel workflow to allow more flexibility
2010-07-22 18:57:45 +01:00
<argument type="service" id="controller_resolver" />
fixed coding standards for XML and YAML files
2010-06-11 09:06:44 +01:00
</service>
[Foundation] added the missing parts of Symfony Foundation
2010-02-17 13:54:36 +00:00
added a cache warmer sub-framework Cache warmer will come in the next commits. To warm up the cache on a production server, you can use the cache:warmup command: ./app/console_prod cache:warmup
2011-01-24 10:16:22 +00:00
<service id="cache_warmer" class="%cache_warmer.class%">
<argument type="collection" />
</service>
added an autoloader that uses a class map A class in Symfony2 can be loaded by four different mechanisms: * bootstrap.php: This file contains classes that are always required and needed very early in the request handling; * classes.php: This file contains classes that are always required and managed by extensions via addClassesToCompile(); * MapFileClassLoader: This autoloader uses a map of class/file to load classes (classes are managed by extensions via addClassesToAutoloadMap(), and should contain often used classes); * UniversalAutolaoder: This autoloader loads all other classes (it's the slowest one).
2011-01-27 13:26:49 +00:00
<service id="cache_warmer.autoload_map" class="%cache_warmer.autoloader_map.class%" public="false">
<tag name="kernel.cache_warmer" />
<argument type="service" id="service_container" />
</service>
[FrameworkBundle] added a comment for the request service This reverts commit c68501cca4151770ba6fb02b39032099d48f6921.
2011-01-23 10:19:16 +00:00
<!--
If you want to change the Request class, modify the code in
your front controller (app.php) so that it passes an instance of
YourRequestClass to the Kernel.
This service definition only defines the scope of the request.
It is used to check references scope.
-->
adds synthetic attribute to definitions This attribute can be used to hint that the service is being injected dynamically at runtime, and not constructed by the DIC.
2011-01-23 11:06:23 +00:00
<service id="request" scope="request" synthetic="true" />
[FrameworkBundle] added a comment for the request service This reverts commit c68501cca4151770ba6fb02b39032099d48f6921.
2011-01-23 10:19:16 +00:00
[FrameworkBundle] registered FileSystem as a service, switched commands to use it
2011-01-13 15:34:41 +00:00
<service id="filesystem" class="%filesystem.class%"></service>
moved common configuration classes to a new Config component
2011-02-10 15:15:51 +00:00
<service id="file_locator" class="%file_locator.class%">
<argument type="service" id="kernel" />
</service>
fixed coding standards for XML and YAML files
2010-06-11 09:06:44 +01:00
</services>
[Foundation] added the missing parts of Symfony Foundation
2010-02-17 13:54:36 +00:00
</container>
Reference in New Issue Copy Permalink