It seems that there is a problem with the path definitions Doctrine\ORM\Mapping\ClassMetadataFactory->getMetadataFor('C:\inetpub\wwwr...') This shouldn't be the absolute path, as Doctrine assumes that is the class name with namespace, so it takes that 'C:\' as namespace So it is a problem with configuration or autoloaders There is a sandbox in the Doctrine which includes a basic working configuration, you can use that as a starting point.
It seems that there is a problem with the path definitions. Doctrine\ORM\Mapping\ClassMetadataFactory->getMetadataFor('C:\inetpub\wwwr...') This shouldn't be the absolute path, as Doctrine assumes that is the class name with namespace, so it takes that 'C:\' as namespace. So it is a problem with configuration or autoloaders.
There is a sandbox in the Doctrine which includes a basic working configuration, you can use that as a starting point.
Hakan Deryal There is no sandbox for Doctrine 2 yet, only for version 1.2 so I cannot do that. I set up my autoloaders and configurations according to this tutorial: snipplr. Com/view/38628/… – Richard Knop Feb 27 at 12:36 I don't know anything about the framework, so can't comment on the guide.
But the errors indicate that problem I mentioned. And there is a sandbox for Doctrine2. In git repo, under tools directory.
– Hakan Deryal Feb 27 at 13:38 Well, I can't find any link to the sandbox on Doctrine website. – Richard Knop Feb 27 at 14:56 doctrine-project. Org/docs/orm/2.0/en/reference/… Its only in the github repo for now it seems.
– Hakan Deryal Feb 27 at 15:03 @Hakan Deryal Well, and the sandbox I have downloaded from the github is not working (there are some files missing) so that's just great. – Richard Knop Feb 27 at 20:20.
After thinking about this a while, I think it is an interesting problem that points out some conceptual issues as well as some opportunities. The reason SchemaTool behaves that way is simple, I think: A mapped superclass is nothing more than a regular php class that inherits its mapping information to the child classes "as if it were defined directly on the child classes". It is mainly a way to "reuse" mapping information without copy/paste.
Hence why it wants to create two tables. However, something else is also probably wrong because it should rather result in an error due to creating the same table twice ("user"). So deriving @Table from a mapped superclass seems to be uncharted territory also.
How/Why this ever worked before as you say is still a mystery to me.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.