Ok I was pretty sure about this reply. When you mean "change the service", do you mean edit the xml file from the WebBundle, or there is an another way to achieve this [1] ?
[1] http://github.com/fabpot/symfony/commit/b057ef613fab4bc06d77bd45d77ed16ba35f7fc8 On Mon, Jun 7, 2010 at 6:00 PM, Fabien Potencier < [email protected]> wrote: > On 6/7/10 4:47 PM, Thomas Rabaix wrote: > >> Thanks Jordi for your reply. >> >> I have updated the subject as the important part still required a reply >> from whom may concern : An helper does not have access to the project >> container. So if I need to overwrite the router helper class with my >> own logic, I can't do much, as other services will be not accessible. >> > > If you want to override the router, change the service and inject any other > service you need. Think dependency injection ;) > > Fabien > > >> >> On Mon, Jun 7, 2010 at 10:26 AM, Jordi Boggiano <[email protected] >> <mailto:[email protected]>> wrote: >> >> On 06.06.2010 23:59, Thomas Rabaix wrote: >> > >> > $container->setParameter('templating.helper.router.class', >> > 'Symfony\Framework\WebBundle\Helper\RouterHelpers'); >> > >> > inside a Bundle::buildContainer call. This solution does not look >> very >> > nice, maybe I forgot something in the web.templating section from >> the >> > config.yml file. >> >> This should be done in config.yml as: >> >> parameters: >> templating.helper.router.class: >> Symfony\Framework\WebBundle\Helper\RouterHelpers >> >> If that fails, try it in config_dev.yml, and if it works then but not >> in >> config, please report a bug. I had the problem a few months back but >> then I didn't try it out since then so I'm not sure if it's been fixed >> or not. >> >> Cheers >> >> -- >> Jordi Boggiano >> @seldaek :: http://seld.be/ >> >> -- >> If you want to report a vulnerability issue on symfony, please send >> it to security at symfony-project.com <http://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] >> <mailto:[email protected]> >> >> To unsubscribe from this group, send email to >> >> [email protected]<symfony-devs%[email protected]> >> >> <mailto:symfony-devs%[email protected]<symfony-devs%[email protected]> >> > >> >> For more options, visit this group at >> http://groups.google.com/group/symfony-devs?hl=en >> >> >> >> >> -- >> Thomas Rabaix >> http://rabaix.net >> >> -- >> 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]<symfony-devs%[email protected]> >> For more options, visit this group at >> http://groups.google.com/group/symfony-devs?hl=en >> > > -- > 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]<symfony-devs%[email protected]> > For more options, visit this group at > http://groups.google.com/group/symfony-devs?hl=en > -- Thomas Rabaix http://rabaix.net -- 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
