DDC-771: EntityGenerator generates wrong use statement in entity file #950

New Issue

admin · 2026-01-22T12:56:58+01:00

admin commented

2026-01-22 12:56:58 +01:00

Originally created by @doctrinebot on GitHub (Aug 27, 2010).

Originally assigned to: @beberlei on GitHub.

Jira issue originally created by user martinsrom:

If I use EntityGenerator with class to extend 'Extension\Doctrine\ORM\ActiveEntity\ActiveEntity' in generated files I have this use statement:

use Extension\Doctrine\ORM\ActiveEntity;

class XXX extends ActiveEntity

and php ends with error. I think the use statement should look like:

use Extension\Doctrine\ORM\ActiveEntity\ActiveEntity;

class XXX extends ActiveEntity

After I repaired this function it works ok:

private function _getClassToExtendNamespace()
{
    $refl = new \ReflectionClass($this->_getClassToExtend());

    return $refl->getNamespaceName() ? $refl->getNamespaceName():$refl->getShortName();
}

to

return $refl->getNamespaceName() ? $refl->getNamespaceName().'\\'.$refl->getShortName():$refl->getShortName();

I'am not sure if it is bug or I am doing something wrong.

Originally created by @doctrinebot on GitHub (Aug 27, 2010). Originally assigned to: @beberlei on GitHub. Jira issue originally created by user martinsrom: If I use EntityGenerator with class to extend 'Extension\Doctrine\ORM\ActiveEntity\ActiveEntity' in generated files I have this use statement: ``` use Extension\Doctrine\ORM\ActiveEntity; class XXX extends ActiveEntity ``` and php ends with error. I think the use statement should look like: ``` use Extension\Doctrine\ORM\ActiveEntity\ActiveEntity; class XXX extends ActiveEntity ``` After I repaired this function it works ok: ``` private function _getClassToExtendNamespace() { $refl = new \ReflectionClass($this->_getClassToExtend()); return $refl->getNamespaceName() ? $refl->getNamespaceName():$refl->getShortName(); } ``` to ``` return $refl->getNamespaceName() ? $refl->getNamespaceName().'\\'.$refl->getShortName():$refl->getShortName(); ``` I'am not sure if it is bug or I am doing something wrong.

admin added the Bug label 2026-01-22 12:56:58 +01:00

admin closed this issue

2026-01-22 12:56:58 +01:00

admin commented

2026-01-22 12:57:00 +01:00

@doctrinebot commented on GitHub (Aug 28, 2010):

Comment created by @beberlei:

fixed formating

@doctrinebot commented on GitHub (Aug 28, 2010): Comment created by @beberlei: fixed formating

admin commented

2026-01-22 12:57:00 +01:00

@doctrinebot commented on GitHub (Aug 28, 2010):

Comment created by @beberlei:

Fixed

@doctrinebot commented on GitHub (Aug 28, 2010): Comment created by @beberlei: Fixed

admin commented

2026-01-22 12:57:01 +01:00

@doctrinebot commented on GitHub (Aug 28, 2010):

Comment created by martinsrom:

After your fix, the EntityGenerator generates this:

use Extension\Doctrine\ORM\ActiveEntity\ActiveEntity;

class XXX extends Extension\Doctrine\ORM\ActiveEntity\ActiveEntity

and it isn't still right. There are two right posibilities:

use Extension\Doctrine\ORM\ActiveEntity\ActiveEntity;

class XXX extends ActiveEntity

or

class XXX extends Extension\Doctrine\ORM\ActiveEntity\ActiveEntity

@doctrinebot commented on GitHub (Aug 28, 2010): Comment created by martinsrom: After your fix, the EntityGenerator generates this: ``` use Extension\Doctrine\ORM\ActiveEntity\ActiveEntity; class XXX extends Extension\Doctrine\ORM\ActiveEntity\ActiveEntity ``` and it isn't still right. There are two right posibilities: ``` use Extension\Doctrine\ORM\ActiveEntity\ActiveEntity; class XXX extends ActiveEntity ``` or ``` class XXX extends Extension\Doctrine\ORM\ActiveEntity\ActiveEntity ```

admin commented

2026-01-22 12:57:02 +01:00

@doctrinebot commented on GitHub (Aug 28, 2010):

Comment created by @beberlei:

ok, i dropped the use statement.

@doctrinebot commented on GitHub (Aug 28, 2010): Comment created by @beberlei: ok, i dropped the use statement.

admin commented

2026-01-22 12:57:03 +01:00

@doctrinebot commented on GitHub (Aug 28, 2010):

Issue was closed with resolution "Fixed"

@doctrinebot commented on GitHub (Aug 28, 2010): Issue was closed with resolution "Fixed"

admin referenced this issue