On Mon, Mar 23, 2009 at 11:13 AM, James Carman <jcar...@carmanconsulting.com> wrote: > On Mon, Mar 23, 2009 at 11:26 AM, Jeremy Thomerson > <jer...@wickettraining.com> wrote: >> Great news James! For those who are looking to decide between the two, how >> does this differ from / improve on the existing wicket-ioc project? > > 1. Much easier to extend. All you need to do is implement the > DependencyProvider interface. > > 2. You *always* use the @Inject annotation. The annotation types > don't change between different dependency provider implementations.
what happens when features of differnet containers need to bleed through? for example Guice's @Inject has an optional() attribute. Since users of wicket-guice use guice's own @Inject it is all transparently supported. if i want to use that feature with syringe will i have to do @syringe.Inject @syringe.guice.Guice(optional=true) Reversely, syringe.Inject offers a name attribute, which afaik, guice does not support... Just trying to figure out how a unified annotation will work with containers that are so different. > 3. The proxying is done using Commons Proxy, so the code is much more > lightweight. you mean syringe does not have the portion of code that deals with cglib? that has been farmed out to commons-proxy? i dont see how this is a differentiating feature though unless you expect your users to work with syringe code that creates proxies? > 4. It uses the new wicket-plugin architecture (another > wicketstuff-core project), so the only restriction it places on your > application class is that it extends WicketPluginApplication. Other > "plugins" (like security, etc.) should be written this way, too. this pattern has proved quiet problematic in the past, and will keep doing so until everybody uses the wicketpluginapplication base class for the plugins they write for wicket. you should support a way of working with syringe without the base class present. -igor > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
