Session.get().getApplication(), also Application.get() will work. it usually helps to listen.
-igor On Tue, Aug 4, 2009 at 1:02 PM, Aaron Dixon<atdi...@gmail.com> wrote: > That seems to provide a solutino for WicketSession access, but what > about access to the Application instance? > > On Tue, Aug 4, 2009 at 1:51 PM, Igor Vaynberg<igor.vaynb...@gmail.com> wrote: >> see WicketSessionFilter >> >> -igor >> >> On Tue, Aug 4, 2009 at 11:49 AM, Aaron Dixon<atdi...@gmail.com> wrote: >>> I am implementing a servlet external to my Wicket application that >>> needs to access my Wicket Application instance itself... >>> >>> Can anyone recommend a clean way to go about this? >>> >>> --------------------------------------------------------------------- >>> 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 >> >> > > --------------------------------------------------------------------- > 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
