That's the exact reason why we're mostly using single app bundle for application logic. Because in any other case we're spending too much time thinking about things that are not actually relevant to the development process - in which bundle to put this entity/form/controller/view, how to name new bundle, how to configure it.
If it's part of non-sharable logic that will live only inside this application, then there's no reason to spend time on making it shared. --- *Konstantin Kudryashov* --- PHP developer, BDD evangelist, Scrum master a: http://about.me/everzet/bio b: http://everzet.com c: https://github.com/everzet On Fri, Feb 8, 2013 at 10:55 AM, Thomas Lundquist < thoma...@redpill-linpro.com> wrote: > On Fri, Feb 08, 2013 at 01:08:44AM -0800, Milos Janjic wrote: > > Hello everyone, > > > > my main question here what is best practice for placing common entities > > (see example below) > > > > We have *UserBundle* and *User* entity in this bundle. > > Also we have *CompanyBundle* and *Company* entity in this bundle. > > So, now we are need to create *Country* entity that is system wide (User > > and Company can set their country). What is the best place for putting > this > > entity? > > > > For now I can only see one solution... to create one more bundle (lets > call > > him *CommonBundle*) and put all entities that are common for all other > > bundles. Is this good thinking? > > I did exactly that, and yes, it's called "CommonBundle" :=) > > It may not be that smart and I've ended up with putting way too much in it > and have to split it into more bundles soon. On the other hand, it's pretty > OK to have a place for starting new bundles. Making bundles for the > smallest > thingie isn't that productive either. So, if it grows and looks like a > bundle, > make it one. > > And it started with FOSUserBundle "needing" a user object and some admin > pages. > > I'll end up with my CommonBundle on github some day, hopefully. Also, > hopefully > as more than one bundle. (Reports and "Contexts" are two obvious > candidates.) > > > Thomas. > > -- > -- > If you want to report a vulnerability issue on Symfony, please read the > procedure on http://symfony.com/security > > You received this message because you are subscribed to the Google > Groups "symfony developers" group. > To post to this group, send email to symfony-devs@googlegroups.com > To unsubscribe from this group, send email to > symfony-devs+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/symfony-devs?hl=en > --- > You received this message because you are subscribed to the Google Groups > "Symfony developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to symfony-devs+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- -- If you want to report a vulnerability issue on Symfony, please read the procedure on http://symfony.com/security You received this message because you are subscribed to the Google Groups "symfony developers" group. To post to this group, send email to symfony-devs@googlegroups.com To unsubscribe from this group, send email to symfony-devs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en --- You received this message because you are subscribed to the Google Groups "Symfony developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to symfony-devs+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
