How do I define an entity which is commonly used several bundles?

Question

I want to create a blogging system in order to practice symfony2, but currently I get a bit confused when creating entities such as user or blog. The reason is the following :

User( or Blog) is commonly used in frontend and backend(admin) (currently I have considered creating FrontendBundle and AdminBundle)
Entity must belong to one bundle.

Currently I have considered the following methods, but what is the best way in this case, or please tell me if there is another way.

Create bundle named 'BlogCommonBundle' and define User entity as "BlogCommonBundle:User".
Define all controllers under 1 bundle, such as 'BlogBundle', so frontend/backend(admin) controllers belong to same bundle.

Why not create an additional UserBundle and make Frontend and Admin dependant on it? — hakre
Thank @hakre for your answer, and I'm sorry for my response was slow, I did not noticed your comment. I had not considered the pattern which you advised at that time. But as Arms advised below, it's new idea for me. — tristar

Steven Mercatante Steven Mercatante · Accepted Answer · 2011-10-04T03:44:36

I think creating a BlogBundle and having multiple controllers for frontend and admin functionality is a good way to handle this. Both controllers would make use of the same entities and repositories, and you can easily firewall your admin actions in the security settings of your application. By keeping everything blog related to one bundle, you maintain good code organization.

The same goes for a UserBundle. It's helpful to remind yourself that a bundle should represent a set of like functionality for an application. So if you have code that fetches blog posts, and allows you to create and manage them, they naturally group together in a single bundle.

How do I define an entity which is commonly used several bundles?

2 Answers