Definitions, aliases, and parameters which are defined in the config_xxx.yml (or files imported into it) always take precedence over definitions, etc. defined by an extension.
Kind regards, Johannes On 8 Feb., 13:45, stof <[email protected]> wrote: > On Tue, 8 Feb 2011 13:42:41 +0100, Lukas Kahwe Smith <[email protected]> > wrote: > > > > > On 08.02.2011, at 13:38, Venzon wrote: > > >>> no i mean fixing the given Extension that currently loads the config > >>> that defines the service. so in this case FrameworkExtension. > >>> as a last resort i think the cleanest solution to change such > >>> parameters if the Extension doesnt support is a Compiler pass. > > >>> regards, > >>> Lukas Kahwe Smith > > >> I have compiler pass defined for my extension but it is executed when > >> all core classes and services are loaded so I dont know how can I > >> change there such basic settings like class names. > > > you can get the definition and totally rewrite it. > > > regards, > > Lukas Kahwe Smith > > [email protected] > > Thus changing the value after the core extension put the definition is > mandatory as the last definition is used. > So a CompilerPass is the only way to be sure to override the core > definition. > > -- > Christophe | Stof -- 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
