Wrong proxy classes check in AbstractManagerRegistry if lazy ghost is enabled

[mba242]

doctrine/orm creates proxy class implementations of various interfaces depending on whether the lazy ghost setting is enabled or not.
ProxyFactory line 116

doctrine/persistence checks a proxy class by its interface.
AbstractManagerRegistry line 176

doctrine/DoctrineBundle doesn't care and intializes doctrine/persistence with the old Proxy interface.
Registry line 30

Doctrine\Persistence\AbstractManagerRegistry->getManagerForClass($proxyClassName) returns null when lazy ghost is enabled.

[burned42]

I was just faced with the same issue after updating the flex recipe which enabled the lazy ghost objects.

And I can also confirm your findings, changing to the used proxy class name to Doctrine\Persistence\Proxy at https://github.com/doctrine/DoctrineBundle/blob/2.8.x/Registry.php#L30 seemed to work for me, though I'm not sure if that's a proper fix or if it would break other things.

A quick fix for me was to disable enable_lazy_ghost_objects again for now.

[mba242]

[...]changing to the used proxy class name to Doctrine\Persistence\Proxy at https://github.com/doctrine/DoctrineBundle/blob/2.8.x/Registry.php#L30 seemed to work for me, though I'm not sure if that's a proper fix or if it would break other things.

I guess it will breaks something in case lazy ghost is disabled. In think it needs the same check like in the ProxyFactory class and give depending interface name to parent.

Anyway - there is a lot around in doctrine universe. I don't know if there more effects.

[nicolas-grekas]

Changing the namespace looks enough to me. PR sent as #1621