@Fabien: Okay, namespaces for annotations, great !
@Jordi: I know how to cope with the problem in the meantime, I was
just wondering if this issue was beeing looked into.
Anyway, thanks for the answers !
On Sep 23, 7:49 am, Fabien Potencier <fabien.potenc...@symfony-
project.com> wrote:
> On 9/23/10 12:04 AM, Pascal Burkhard wrote:
>
> > After some looking into it I saw that the problem is that @Collection
> > is also used by Doctrine MongoDB Mapping and it does not like it.
>
> We are indeed aware of the problem and we are working on the solution.
> It will consist of a default prefix for annotations. So, your code would
> look like some like the following (names are not definitive yet):
>
> /**
> * @orm:EmbedMany(targetDocument="Application\ChronoTextsBundle\Document
> \ChronoKeyword")
> * @validation:Validation({ @validation:Collection(
> * fields = {
> * "keyword" = @NotNull
> * },
> * allowMissingFields = true,
> * allowExtraFields = true
> * )})
> */
> private $keywords;
--
If you want to report a vulnerability issue on symfony, please send it to
security at symfony-project.com
You received this message because you are subscribed to the Google
Groups "symfony developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/symfony-devs?hl=en
