And its just handy.. You can get to the application by one call everywhere in your code. Of couse we could have done with one threadlocal like RequestCycle and Application and Session can be got from there. But those 3 are just handy quick accessed objects
On 9/26/08, James Carman <[EMAIL PROTECTED]> wrote: > On Fri, Sep 26, 2008 at 7:28 AM, Takeshi Matsuba <[EMAIL PROTECTED]> wrote: >> Hi all. >> >> I understand that there is one Application class instance per >> WicketFilter. >> So, I can use Application class like on memory database. >> (Wicket In Action too. ) >> >> I read source. I notice that Application class instance set ThreadLocal. >> I understand that value of threadLocal is Singleton per request in >> Servlet world. >> Can I use Application class like Singleton per WicketFilter? >> And why set to ThreadLocal? > > You could conceivably have two different Wicket applications running > within the same webapp. I suppose that's why the access is based on a > ThreadLocal. > > --------------------------------------------------------------------- > 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]
