On 15.11.2010, at 13:12, Fabien Potencier wrote: > On 11/15/10 6:54 PM, Jeremy Mikola wrote: > >> And perhaps for bundles that might wish to just replace the >> functionality of a built-in Symfony listener (like exception handling), >> a focused disconnect() would prove useful. > > In that case, I think changing the class (easy with the DIC) or removing the > registration is a better way. > > Anyway, thanks for sharing your use cases, this is really appreciated. > > I think that disabling the registration is probably the best thing to do > instead of disconnecting a listener. What do you think?
Yes, I also think that in Symfony2 there are other ways to do this. Obviously having to replace (or extend/wrap) the original service is not ideal either, but seems cleaner than undoing work that was done previously. Also while its not the magic silver bullet, the adoption of DVCS's like git to me have accelerated the adoption of patches upstream and the easiness to in the worst case maintaining forks that consist of one or two patches kept in sync with upstream. 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
