On 4/13/11 3:08 PM, [email protected] wrote:
Hi,
I am not in favor of doin this, mainly because this follows a strict 1-1
alias namespace. When you ask me to relax again the validation, it
sounds to me something like being against PSR-0. It's the same thing as
autoloader with 1 ns - 1 directory.
The Symfony autoloader allows for the same namespace to be hosted in
different directories. That's really useful for instance if you want to
use a few Symfony components. They are all in the same namespace, but
you don't necessarily need to get them all.
Fabien
But if it's common sense to allow it, my opinion we can make ns alias
support an array and do a loop to validate.
Cheers,
Em 13/04/2011 08:50, "Lukas Kahwe Smith" <[email protected]
<mailto:[email protected]>> escreveu:
>
> Hi,
>
> So what are we going to do about this?
>
> I dont think that we want to fork the annotation parser.
>
> regards,
> Lukas
>
> On 07.04.2011, at 10:42, Johannes Schmitt wrote:
>
> > A further complication is that some annotations are parsed while
the DI container is compiled, so a parser could not be set-up using the
container, but we would need a separate mechanism for this.
> >
> > If we change the namespace, then I think it only makes sense if we
change it for both bundles, for example @framework/@security.
> >
> > A third option which was not mentioned yet is to fork the
annotation parser, and adapt it to our needs.
> >
> > Kind regards,
> > Johannes
> >
> >
> > On Thu, Apr 7, 2011 at 10:36 AM, Christophe COEVOET <[email protected]
<mailto:[email protected]>> wrote:
> > Le 07/04/2011 10:20, Lukas Kahwe Smith a écrit :
> >> Hi,
> >>
> >> Right now MongoDB ODM cannot be used together with both
FrameworkExtra/SecurityExtra due to changes in Doctrine Common master.
MongoDB ODM however requires Doctrine Common master because the
interfaces where added only there.
> >>
> >> For more information on the issue see:
> >>
> >> http://www.doctrine-project.org/jira/browse/DCOM-45
> >>
> >>
> >> Now one solution would be to "fix" Doctrine Common master to allow
registering multiple handlers for the same annotation prefix.
> >> Another one, which I would prefer is for
FrameworkExtra/SecurityExtra to use different prefixes, since I find it
a bit confusing that they are both using the same prefix.
> >>
> >>
> > The first solution would require changing Doctrine Common to allow
several namespaces for an alias in the parser and reusing the same
parser in both bundles. The second part would require to handle this at
the framework level as SecurityExtra and FrameworkExtra should both work
when the other is not available which forbid defining the parser in one
bundle and reusing it in the other.
> >
> > So I would also vote for a different namespace (what about @security ?)
> >
> > --
> > Christophe | Stof
> >
> >
> > --
> > If you want to report a vulnerability issue on symfony, please send
it to security at symfony-project.com <http://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]
<mailto:[email protected]>
> > To unsubscribe from this group, send email to
> > [email protected]
<mailto:symfony-devs%[email protected]>
> > For more options, visit this group at
> > http://groups.google.com/group/symfony-devs?hl=en
> >
> >
> > --
> > If you want to report a vulnerability issue on symfony, please send
it to security at symfony-project.com <http://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]
<mailto:[email protected]>
> > To unsubscribe from this group, send email to
> > [email protected]
<mailto:symfony-devs%[email protected]>
> > For more options, visit this group at
> > http://groups.google.com/group/symfony-devs?hl=en
>
> Lukas Kahwe Smith
> [email protected] <mailto:[email protected]>
>
>
>
> --
> If you want to report a vulnerability issue on symfony, please send
it to security at symfony-project.com <http://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]
<mailto:[email protected]>
> To unsubscribe from this group, send email to
> [email protected]
<mailto:symfony-devs%[email protected]>
> For more options, visit this group at
> http://groups.google.com/group/symfony-devs?hl=en
--
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
--
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
