Hi, You can use org.apache.wicket.guice.GuiceComponentInjector#GuiceComponentInjector(Application app, Injector injector) constructor. I.e. in MyApp#init() do:
getComponentInstantiationListeners().add(new GuiceComponentInjector(this, injectorReadFromServletContext)) On Thu, Oct 10, 2013 at 10:16 AM, Martin Dietze <d...@fh-wedel.de> wrote: > On a legacy project, there are two web frameworks in use, one > for the frontend, one for the backoffice application. This > project already uses Guice which is instanciated by a > ContextListener which also does some initialisation code, like > pulling up some particular Guice beans. > > Now in this project we want to rewrite one of the two frondends > using Wicket. I would like to set up Wicket in a way that it > uses the existing Guice infrastructure. The examples and > tutorials I've found in the web so far always assume that Guice > initialisation (i.e. creation of the injector) goes along with > Wicket initialisation which does not seem to fit to what I am > doing. > > Thus I wonder if someone can tell me how I need to configure > Wicket to use the existing Guice injector? > > Any hint appreciated! > > M'bert > > -- > ----------- / http://herbert.the-little-red-haired-girl.org / > ------------- > =+= > Perl ist der geglückte Versuch, einen braindump direkt ausführbar zu > machen. -- Lutz Donnerhacke in dasr > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
