So, your "itch" or usecase is that you're trying to use Wicket in a way it was not intended.
On Wed, May 19, 2010 at 3:48 PM, Adriano dos Santos Fernandes <adrian...@gmail.com> wrote: > On 19/05/2010 16:36, James Carman wrote: >> >> What itch are we trying to scratch, here, anyway? When do folks need >> access to the Application object outside of a request thread? What is >> the usecase? >> > > I have a piece of code that runs in a timer, and renders a page to a string > to be sent via email. So I do need the app object to make a session. I do > catch it from a static field. > > The code (that is probably inspired in something in the wiki) is not very > clear, needing mock objects. I do think Wicket could have a way to simplify > it, but not introducing leaks that's know to happen with Java system classes > way of work, as I shown. > > > Adriano > >
