I'm answering to myself, but I found a way to handle this:
http://docteurklein.posterous.com/36073492
--
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 u
A Paginator is probably not an object you want to manage with the DIC.
The DIC is good at managing "global" objects like a logger, the user
(from the session), a database connection, ... all the objects for which
you only need one instance. For everything else, the DIC is not the
solution (like yo
Ok, it confirms what I was thinking.
But one of the goals of DI is to give flexibility and externalize (or
"invert") the class instanciations too.
So what if the end user wants to change the Paginator class ?
Should I set the class name as a DI parameter and then use it to
create my class ? examp
On 12/6/10 9:06 PM, Florian wrote:
Ok I should have reformulated my question:
I know it's actually impossible to do that, but the goal of my
question is: How to bypass the problem ?
A Paginator is probably not an object you want to manage with the DIC.
The DIC is good at managing "global" obj
Ok I should have reformulated my question:
I know it's actually impossible to do that, but the goal of my
question is: How to bypass the problem ?
Do I have to modify the lib to work with setters injection ?
On Dec 6, 8:59 pm, Florian wrote:
> Hi,
>
> simple question:
>
> Is it possible to inje
