On 17.12.2010, at 13:27, Leon van der Ree wrote: > So all in all I had to write > - the service container xml > - write a CmsExtension-class with functions that I don't use > - and mention the alias in my config.yml in order to make the > container config loaded > > while the structure of the service container xml is exactly the same > as the one for the routing from Symfony, I would have expected this > could be done a little easier. Maybe only writing the service > container xml, that gets loaded automatically when placed in the > correct folder of your bundle, or if this is too much magic, adding a > simple instruction somewhere (E.G. in the Bundle\CmsBundle\CmsBundle > class ) to define where the service container xml is located. > > Am I maybe missing something, or is there still some room to improve > this.
All services are provided by a Bundle which should offer the necessary means to customize its services. Now for services that you create yourself (or where you extend existing services) they obviously must be provided somehow and the means to do that is a Bundle. Now it wouldn't make sense to automatically load all Bundles, because you could have multiple frontend controllers in one repo that do not all need the same Bundle. So I dont really see any way to simplify the process. You need to configure your new service. The code and the config need to be wrapped into a Bundle. The Bundle needs to be loaded. If this is too much work and you just want everything to be loaded. Create a Bundle once and then drop everything you ever do for any of the front controllers in there. regards, Lukas Kahwe Smith [email protected] -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com You received this message because you are subscribed to the Google Groups "symfony developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en
