> Hi Eelco -- My colleague and I were thinking that putting them all in the > WebApplication > would make it easier to mock services for unit testing with WicketTester.
Alternatively, you could use e.g. InjectorHolder.setInjector(new MockSpringInjector()); like is documented in org.apache.wicket.injection.web.InjectorHolder (at least it is in Wicket 1.3 which I am using). That's a bit more flexible and you don't have to worry about cases where someone (colleague?) uses @SpringBean directly and thus compromises your test strategy). Eelco --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
