Where does the container need access to annotation reader? On Sun, 3 Jul 2011 12:47:50 +0200 Johannes Schmitt <schmitt...@gmail.com> wrote:
> boot() is already too late, it would need to be done in the constructor, but > I don't think that the bundle classes are the right place anyway. > > We can just add one line to the autoload.php and register Symfony's > autoloader with the AnnotationRegistry. Then individual bundles don't need > to care about this, and after all we are setting up auto-loading so > autoload.php seems like the most natural place to do this. > > Johannes > > > On Sun, Jul 3, 2011 at 12:30 PM, Christophe COEVOET <s...@notk.org> wrote: > > > Le 03/07/2011 08:43, Benjamin Eberlei a écrit : > > > > I merged the code for annotation registries now and released Doctrine 2.1 > >> rc3. > >> http://www.doctrine-project.**org/blog/doctrine-2-1-rc3<http://www.doctrine-project.org/blog/doctrine-2-1-rc3> > >> > >> I will try to make a PR to Symfony standard repo to adjust for this change > >> today. > >> > >> The question is if we want to configure the annotation library inside the > >> framework bundle or let developers do this in autoload.php > >> > >> The minimal config for autoload.php would only require two loc so its very > >> simple. > >> > >> On the other hand, each bundle knows its own annotation needs and could > >> register the relevant information in Bundle::boot() > >> > >> Thoughts? > >> > > +1 to put this in the boot() method of the bundle as this job should be > > done by the bundle, not by the end user. > > > > -- > > Christophe | Stof > > > > -- > > 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 symfony-devs@googlegroups.com > > To unsubscribe from this group, send email to > > symfony-devs+unsubscribe@**googlegroups.com<symfony-devs%2bunsubscr...@googlegroups.com> > > For more options, visit this group at > > http://groups.google.com/**group/symfony-devs?hl=en<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 symfony-devs@googlegroups.com > To unsubscribe from this group, send email to > symfony-devs+unsubscr...@googlegroups.com > 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 symfony-devs@googlegroups.com To unsubscribe from this group, send email to symfony-devs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en
