Le 02/02/2011 20:13, Gustavo Adrian a écrit :
Yes, but the thing (in my case) is that being A = ModuleManagerBundle,
each of my module bundles (B and C in this example) has to depend on
it. The problem is that each module could be mandatory or optional.
So, having: C extends B extends A, and B being an optional module,
removing it would break the app, because C extends B.
My current solution is handling dependencies on my module manager
bundle. I just needed to access the ModuleManagerBundle's services
(which thanks to the CompilerPass class I can handle it now), control
module's dependencies and the order in which JS are loaded, based on
this dependency tree. I don't use templates so with a little tweak in
my ModuleManagerBundle made the trick for now.
Thanks a lot for your help guys!
Inherinting from a bundle has nothing to do with dependencies. This is
just the way to override templates and (maybe) translations.
Your JS files does not overrides each other as they have different names
(according to your previous mail) so the order they are loaded in the
page only depends of the order used when writing the <script> tag in
your page (which only depends of your template).
Each bundle can define its own service using other services as argument.
And if you need to be able to pass services defined in the ModuleBundle
to a service defined in ModuleManagerBundle without knowing their id in
ModuleManagerBundle, the good way to do so is to use a tag and a
CompilerPass. And again, this is not bundle inheritance.
--
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
