speaking of moving it to Apache.. currently we have some inconsistencies between Spring and Guice integrations and users ask from time to time : - why we don't use jsr330 @javax.inject.Inject since both Spring and Guice support it. With CDI I think javax.enterprise.inject.Inject is used which is yet another ... - is it possible to not proxy the injected object (we have a ticket with patch for Spring for that but not for Guice)
now with CDI I see more: - why Injector.get().inject(me) doesn't work ? --- because it needs BeanManager, but since it is reachable from ServletContext then it should be OK --- because it needs the class - OK, use me.getClass() for that - why Spring/Guice doesn't support @PostConstruct ? So my question is: should we try to make them consistent with each other or we should provide minimal integration and give the user the possibility to use the full power of his favorite DI framework ? On Wed, Nov 16, 2011 at 10:52 AM, Igor Vaynberg <igor.vaynb...@gmail.com> wrote: > sure > > -igor > > On Wed, Nov 16, 2011 at 12:49 AM, Martijn Dashorst < > martijn.dasho...@gmail.com> wrote: > >> On Tue, Nov 15, 2011 at 7:00 PM, Igor Vaynberg <igor.vaynb...@gmail.com> >> wrote: >> > if you want to learn how to use CDI with Wicket i just wrote a short blog >> > about it: >> > >> > https://www.42lines.net/2011/11/15/integrating-cdi-into-wicket/ >> >> Can we use it for the documentation of the CDI project (when we >> migrate it to apache)? >> >> Martijn >> >> -- >> Become a Wicket expert, learn from the best: http://wicketinaction.com >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >> For additional commands, e-mail: users-h...@wicket.apache.org >> >> > -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
