On 01.02.2011 15:02, Thomas Rabaix wrote: > > On 1 févr. 2011, at 13:17, Jordi Boggiano wrote: > >> On 01.02.2011 09:26, Benjamin Eberlei wrote: >>> don't know if anybody mentioned it yet, but overriding models is not >>> possible anyways, at least not with the DoctrineBundle. >>> >>> It would just be too complicated to guarantee it works internally, say for >>> example you have Entity A you want to override, but it is using >>> Inheritance, so B extends A and C extends A. Now how would overriding A >>> work? There is just no sane way to do it. >> >> I don't usually want to use any model provided by a third party anyway, >> but just for the sake of the discussion, if everyone used the namespace >> aliases, you could have FooBundle:Entity and then in your config you can >> just redefine FooBundle: alias to one of your bundle namespaces, >> therefore overriding the base bundle files. Of course that means you'd >> have to copy all the bundle's models in your overriding bundle. But it's >> at least one way it should be doable, no? >> > Ok but if you don't want to use a model provided by a third party, why are > you using the bundle? a bundle will never match client's requirement, so you > will need to be able to extends all part of the MVC design pattern.
That's my point, a bundle that provides MVC stuff will never match what I want, so I have very limited interest in those type of Bundles. That being said, did you read the rest of my mail? It somewhat provided a solution (via best practice) to your problem. 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 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
