Usually my "Service"s get extracted into a dedicated Component, e.g:
Company\Component\Messaging and I use those classes as my services, but in case I need to overload some of them to be bundle or application specific, I create the same namespace under my byndle, e.g.: Company\MyBundle\Messaging\SomeClass overloads Company\Component\Messaging\SomeClass This is similar to how Symfony2 uses its native components in bundles. Thoughts? On Wed, Oct 6, 2010 at 10:27 AM, Miha Vrhovnik <[email protected]>wrote: > Hi *, > > I was wondering if somebody had any thoughts on what would be the > "best practice" to structure the Bundles when you need to have a > standard app and a service part of it and most of the app also needs > to be exposed as service. > I've come up with following Bundle structure: > > \src\Service - services > \src\Bundle - the actual implementation (jsonrpc,xmlrpc...) > \src\Application - application bundles that reuse bundles from \src > \Service > > Regadrs, > Miha > > -- > 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 > -- *Bulat Shakirzyanov* | Software Alchemist *t:* @avalanche123 *g:* github.com/avalanche123 *b:* avalanche123.com *e:* [email protected] -- 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
