Warning from class_parents() in ClassMetadataFactory

[pdugas]

If I had to guess, I'd suggest this is due to the current state of flux with Doctrine and Symfony lately but I've tried to track it down for much of today without success. Figured I'd drop you an issue in case it rings any bells for you.

I'm getting the following warning when I run "app/console doctrine:schema:create"

Warning: class_parents(): Class Stof\DoctrineExtensionsBundle\Entity\Stof\DoctrineExtensionsBundle\Entity\AbstractClosure does not exist and could not be loaded in /home/pdugas/work/vendor/doctrine/lib/Doctrine/ORM/Mapping/ClassMetadataFactory.php line 223

I'm working from the 2.0BETA2 version of Symfony Standard using the included bin/vendors.php script. I've tried changing the VERSION to 2.0.0NEXT and changing the bin/2.0.0NEXT.deps file to use "master" instead of "2.0.5" for the doctrine version. I've also tried making sure I've got "master" versions of DoctrineExtensionsBundle and gedmo-doctrine-extensions. Just can't seem to shake this fault.

[pdugas]

For sanity sake, I dropped back to a clean version of Symfony_Standard_2.0.0BETA2.tgz. Using the stock config, I ran the doctrine:schema:create command and got "No Metadata Classes to process" as I expect given that I've not created any entity classes. I added the StofDoctrineExtensionsBundle line in app/AppKernel.php and both the 'Stof' and 'Gedmo' namespaces in app/autoload.php. I added the following to bin/deps:

/ gedmo-doctrine-extensions http://github.com/l3pp4rd/DoctrineExtensions.git
/bundles/Stof DoctrineExtensionsBundle http://github.com/stof/DoctrineExtensionsBundle.git

I didn't set any versions on bin/2.0.0BETA2.deps so the bin/vendor.php scrip pulled origin/HEAD for these. I tried it once with the stock VERSION file and again after changing VERSION to 2.0.0NEXT. In both cases, running the doctrine:schema:create command generated the same error.

[pdugas]

I think the issue may be with the names of the files in Resources/config/doctrine. They do not need the namespace prefixes so Stof.DoctrineExtensionsBundle.Entity.AbstractClosure.orm.xml becomes AbstractClosure.orm.xml, etc.

[j]

I got the same error initially.

[l3pp4rd]

Class Stof\DoctrineExtensionsBundle\Entity\Stof\DoctrineExtensionsBundle\Entity\AbstractClosure clearly shows that something is wrong with the mapping. Try to rename those xml files

[pdugas]

Sorry. I should have mentioned in my earlier comment that renaming the *.orm.xml files to remove the "Stof.DoctrineExtensionsBundle.Entity." prefix did in fact get me past that fault.

[stof]

The issue is that the naming change was merged yesterday when I was in a place without Internet access. I will update the bundle accordingly

[stof]

I just commited the file renaming.

[pdugas]

Don't mean to be a pest but I don't think this commit went through. I see commits for a couple later issues but this one seems to be missing.

[stof]

sorry, I messed the push. It is done now.

[pdugas]

np, thx much for your efforts. good stuff.

Paul Dugas • Dugas Enterprises, LLC • Computer Engineer

522 Black Canyon Park, Canton GA 30114 •
Paul@DugasEnterprises.compaul@dugasenterprises.com •
+1.404.932.1355

On Tue, May 24, 2011 at 11:55 AM, stof <
reply@reply.github.com>wrote:

sorry, I messed the push. It is done now.

Reply to this email directly or view it on GitHub:
https://github.com/stof/DoctrineExtensionsBundle/issues/34#comment_1229262