Question

I’d like to use, something like:

$em = $this->getEntityManager();

Inside a Entity.

I understand I should do this as a service but for some testing purposes, I want to access it from an Entity.

Is it possible to achieve that?

I’ve tried to:

$em = $this->getEntityManager();
$profile_avatar = $em->getRepository('bundle:Perfils')->findOneByUser($this-getId());

But isn’t working.

Fatal error: Call to undefined method
Proxies\webBundleEntityUserProxy::getEntityManager() in
/opt/lampp/htdocs/web/src/Pct/bundle/Entity/User.php on line
449

Why am I trying to do it this way?

I’ve 3 kinds of users: Facebook, Twitter and MyOwnWebsite users. Each of them have differents avatar which links facebook’s profile, twitter’s or otherwise, if its myownwebsite user, I retrieve the avatar from a URL in a database. For now, I don’t want to create a service, because I’m just trying to make it working, to test it, not to create a final deployment. So this is why I’m trying to call Entity manager from an Entity. I don’t want, by now, to modify configuration files, just this entity.

Answer 1

As pointed out (again) by a commenter, an entity manager inside an entity is a code smell. For the OP’s specific situation where he wished to acquire the entity manager, with the least bother, a simple setter injection would be most reliable (contrary to my original example injecting via constructor).

For anyone else ending up here looking for a superior solution to the same problem, there are 2 ways to achieve this:

1. Implementing the ObjectManagerAware interface as suggested by https://stackoverflow.com/a/24766285/1349295

   use Doctrine\Common\Persistence\ObjectManagerAware;
   use Doctrine\Common\Persistence\ObjectManager;
   use Doctrine\Common\Persistence\Mapping\ClassMetadata;
   use Doctrine\ORM\Mapping as ORM;
   
   /**
    * @ORM\Entity
    */
   class Entity implements ObjectManagerAware
   {
       public function injectObjectManager(
           ObjectManager $objectManager,
           ClassMetadata $classMetadata
       ) {
           $this->em = $objectManager;
       }
   }
   

2. Or, using the @postLoad/@postPersist life cycle callbacks and acquiring the entity manager using the LifecycleEventArgs argument as suggested by https://stackoverflow.com/a/23793897/1349295

   use Doctrine\Common\Persistence\Event\LifecycleEventArgs;
   use Doctrine\ORM\Mapping as ORM;
   
   /**
    * @ORM\Entity
    * @ORM\HasLifecycleCallbacks()
    */
   class Entity
   {
       /**
        * @ORM\PostLoad
        * @ORM\PostPersist
        */
       public function fetchEntityManager(LifecycleEventArgs $args)
       {
           $this->setEntityManager($args->getEntityManager());
       }
   }
   

Original answer

Using an EntityManager from within an Entity is VERY BAD PRACTICE. Doing so defeats the purpose of decoupling query and persist operations from the entity itself.

But, if you really, really, really need an entity manager in an entity and cannot do otherwise then inject it into the entity.

class Entity
{
    private $em;

    public function __contruct($em)
    {
        $this->em = $em;
    }
}

Then invoke as new Entity($em).