I would like to colocate a wicket application with a servlet. What I want is
for the servlet to have access to the wicket session. Looking at the code I
see that Session.get() uses thread-specific storage, so I want the wicket
filter to intercept all requests.
Next, I want to make sure that
Hi Erik,
Non-bookmarkable links either start with /resources or take the form
/?wicket...
You could indeed manage that by creating your own RequestCodingStrategy,
but having done so a couple of times, I would like to warn you not to
tweak too much. In Wicket 1.5 it is probably going to be a
see WicketSessionFilter
-igor
On Mon, Jul 26, 2010 at 11:37 AM, Erik Brakkee erik.brak...@gmail.com wrote:
I would like to colocate a wicket application with a servlet. What I want is
for the servlet to have access to the wicket session. Looking at the code I
see that Session.get() uses
On Mon, Jul 26, 2010 at 9:15 PM, Igor Vaynberg igor.vaynb...@gmail.comwrote:
see WicketSessionFilter
-igor
Indeed, looking at the source code of WicketFilter, it does not seem to set
the session for the current thread when one of the ignored paths is used.
