On Tue, Mar 22, 2011 at 10:53 AM, Robert Campbell <[email protected]> wrote:
> I don't want to create a new topic for this. Trying to setup security in my
> application, I came across this in the documentation:
>
> /**
> * @Entity(repositoryClass="SecurityBundle:UserRepository")
> */
> class User implements UserInterface
> {
> // ...
> }
>
>
> should it be:
>
> /**
> * @orm:@Entity(repositoryClass="SecurityBundle:UserRepository")
> */
> class User implements UserInterface
> {
> // ...
> }
>
> as everything else is prefixed with @orm that is orm related.
>
>
The "@" before Entity is redundant (I would think it'd be invalid, even),
but you are correct that the "orm:" prefix is missing. I'll submit a PR to
the docs for this, once I research the FQN problem below. The short bundle
name syntax was supported in the past, but perhaps something recently
changed and broke it. It's also possible that it only works for bundles
that are declared in the Doctrine bundle config's mappings block, but I'm
guessing there.
> Also I got exceptions using this format:
> * @orm:@Entity(repositoryClass="SecurityBundle:UserRepository")
>
> I had to use a fully qualified class name in order to keep my application
> from croaking. Some clarity on this would be helpful.
>
>
--
jeremy mikola
--
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
