Some of the things that I need to have injected aren't being injected into "components." For instance, I'm working on an AcegiAuthorizationStrategy which is going to require an AuthenticationProvider from Acegi. I suppose I could look up the AuthenticationProvider in my web application class and pass that into my AcegiAuthorizationStrategy constructor when I set it on my ISecuritySettings instance.
I come from the Tapestry/HiveMind world where everything was weaved together via HiveMind. I guess I'm just used to it. In this case, I'm not using HiveMind (yet, that's coming soon too), but I'm using Spring. I really liked the way HiveMind allowed me the capability of providing a default service implementation and drop-in jars could override that functionality if they saw fit. That makes writing "plugins" very easy. On 2/18/08, Timo Rantalaiho <[EMAIL PROTECTED]> wrote: > On Mon, 18 Feb 2008, James Carman wrote: > > If I want to use wicket-spring, but I want to try to let Spring wire > > everything together, what is the best way to do so? I realize that > > I think that it's not a good idea to try to configure > Wicket using Spring (what would be the added value?) but > just use Spring (or Guice :)) for injecting dependencies to > Wicket components. > > Best wishes, > Timo > > -- > Timo Rantalaiho > Reaktor Innovations Oy <URL: http://www.ri.fi/ > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
