Annotations used for service deffinitions and customizable property injection

Hi!

I would like to ask if something is wrong in this way how to define services (see examples).

For larger projects, it is clearer to me. And it gives more options about property injection.

Examples:

/**
 * @Service
 */
class UsersManager {
    /** @InjectDao("\App\Model\Entities\User")  */
    public $userDao;

    /** @InjectDao("\App\Model\Entities\Group") */
    public $groupDao;

    ....
}

or

/**
 * @EventSubscriber
 */
class TestEventSubscriber extends Nette\Object implements Kdyby\Events\Subscriber
{
    ...
}

Used annotations:

/**
 * @Annotation
 */
class Service implements IServiceAnnotation
{
	public function createServiceDefinition($class)
	{
		$definition = new ServiceDefinition();
		$definition->setClass($class);
		$definition->setInject(TRUE);
		return $definition;
	}
}

/**
 * @Annotation
 */
class EventSubscriber implements IServiceAnnotation
{
	public function createServiceDefinition($class)
	{
		$definition = new ServiceDefinition();
		$definition->setClass($class);
		$definition->setInject(TRUE);
		$definition->addTag('kdyby.subscriber');
		return $definition;
	}
}

/**
 * @Annotation
 */
class InjectDao implements IInjectAnnotation {

	const ENTITY_MANAGER_CLASS = 'Kdyby\Doctrine\EntityManager';

	private $entityName;

	public function __construct(array $parameters) {
		if (!isset($parameters['value'])) {
			throw new InvalidArgumentException("Expected entity name.");
		}
		$this->entityName = $parameters['value'];
	}

	public function createInjectStatement(Property $property) {
		return new Statement('$this->getByType(?)->getDao(?)', array(self::ENTITY_MANAGER_CLASS, $this->entityName));
	}
}

I tried to write an extension for the compiler: https://github.com/…-annotations

You think it's a good idea? Or are there some hidden risks that I did not realize?