http://www.doctrine-project.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=fixVersion+%3D+%222.2.2%22+AND+project+%3D+DDC+AND+resolution+%3D+Unresolved+ORDER+BY+updated+DESC An XML representation of a search request en-us 5.2.7 850 21-02-2013 http://www.doctrine-project.org/jira/browse/DDC-1698 Doctrine 2 - ORM <p>Starting with Doctrine 2.2, the Proxy classes have inconsistent naming with their file name, which raises problems with class autoloading.<br/> For example, a class named <b>Application\Model\User</b> creates the following proxy class:</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>Application\Proxy\__CG__\Application\Model\User </pre> </div></div> <p>This class is located in the following file:</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>Application/Proxy/__CG__ApplicationModelUser.php </pre> </div></div> <p>But whe we serialize such an entity, then unserialize it in another session, the framework autoloader expects the class to be located in:</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>Application/Proxy/__CG__/Application/Model/User.php </pre> </div></div> <p>But it is not.<br/> As a result, a __PHP_Incomplete_Class is created instead of the expected proxy class.</p> <p>I'm not sure whether this is an intended behavior, but I would assume this is a bug.</p> Irrelevant DDC-1698

Inconsistent proxy file name & namespace result in __PHP_Incomplete_Class when unserializing entities

Documentation Major Reopened Unresolved All Benjamin Eberlei Benjamin Morel Tue, 13 Mar 2012 00:11:42 +0000 Sun, 6 Jan 2013 13:18:41 +0000 2.2 2.2.1 2.2.2 ORM 0 2 <p>It looks like there is an even broader problem with the new _<em>CG</em>_ prefix; the PSR-0 standard for autoloading states that the underscores should be handled this way:</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>\namespace\package\Class_Name =&gt; {...}/namespace/package/Class/Name.php </pre> </div></div> <p>Which means that in the above example, it could even expect the file to be located in:</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>Application/Proxy///CG///Application/Model/User.php </pre> </div></div> <p>... which is far away from the actual location.<br/> Upgrade to 2.2 broke this code, for us.</p> <p>Proxy classes do not follow PSR-0. For the case unserializing objects we should provide an extra autoloader i guess.</p> <p>See here how symfony does it <a href="https://github.com/doctrine/DoctrineBundle/blob/master/DoctrineBundle.php#L57" class="external-link">https://github.com/doctrine/DoctrineBundle/blob/master/DoctrineBundle.php#L57</a></p> <p>See <a href="https://github.com/doctrine/doctrine2/commit/9b4d60897dfc7e9b165712428539e694ec596c80" class="external-link">https://github.com/doctrine/doctrine2/commit/9b4d60897dfc7e9b165712428539e694ec596c80</a> and <a href="https://github.com/doctrine/orm-documentation/commit/01381fae1ff3d4944086c7cfe46721925bf6ca15" class="external-link">https://github.com/doctrine/orm-documentation/commit/01381fae1ff3d4944086c7cfe46721925bf6ca15</a></p> <p>Thanks for the quick fix, Benjamin.<br/> However, I have to admit that I'm not fully happy with the fix, as we (and probably many others) are not using the Doctrine autoloader.<br/> I supposed that the purpose of PSR-0 was precisely not to be tied to a particular autoloader implementation, and this benefit is lost with this version of Doctrine.</p> <p>You mentioned in the doc that the proxies are not PSR-0 compliant "for implementation reasons"; as this was working fine before 2.2, could you please explain what requirement prevents Doctrine from keeping the previous naming convention?</p> <p>In 2.1 the proxies are not PSR-0 compatible themselves, however their class naming is simpler.</p> <p>In 2.2 we changed proxy names so that you can derive the original name of the proxy by searching for the _<em>CG</em>_ flag. This flag obviously contains the __ chars that some PSR autoloaders detect as directory seperators. I agree this is an unfortunate decision, but it was done this way.</p> <p>I do think however that we can automatically register the proxy atuoloader (if not yet done) in EntityManager#create(). This would hide this fact from developers automatically.</p> <p>@Benjamin Eberlei<br/> In 2.3 we still have to manually call Autoloader::register() before unserializing entities that may contain proxies.<br/> So EntityManager::create() still doesn't register it. Is there a plan to add this feature?</p> <p><a href="http://www.doctrine-project.org/jira/secure/ViewProfile.jspa?name=benjamin" class="user-hover" rel="benjamin">Benjamin Morel</a> Not at the moment, seems too dangerous for me since it might produce race conditions. This should really be done in the bootstrap of the system.</p> <p>We need to document this though.</p> <p>Ok, thanks for your answer!</p>