I think the best solution would be for the blog bundle to depend on something like DoctrineUserBundle.
This allows the application to extend this user for its own purposes, and if the BlogBundle wants a DoctrineUserBundle:User, any extended entity will also be excepted. t On Thu, Nov 4, 2010 at 09:37, Thomas Rabaix <[email protected]> wrote: > Hello, > > Here a simple use case : a blog bundle refers to an Author, an author is an > instance of an User defined in an UserBundle. Now, I want to be able to > change this external dependency from the BlogBundle. > > The only solution I get so far is by using an EventSubscriber > > https://gist.github.com/661824 > > I also remove the type hinting in the Blog::setUser definition and remove > the mapping definition from the blog xml file. > > Do you think it is the correct way to implements this ? > > -- > 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]<symfony-devs%[email protected]> > For more options, visit this group at > http://groups.google.com/group/symfony-devs?hl=en > -- 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
