Hi,
The problem is that your web service and WicketFilter are configured to
listen on different filter paths, e.g. /webservice/* and /wicket/*.
If there was a request to /wicket/* that had bound a Session then the call
to /webservice/* will be OK, but otherwise it will fail because while
trying to
Thanks for all your efforts.
I think the problem was due to a missing session-timeout configuration.
In my app Jetty is started programmatically, including the Wicket filter
setup.
However, since there is no web.xml there was no session-timeout config.
I have added this now and things seem to be b
Thanks for sharing this information!
I'll wait some more and most probably close the ticket as "Cannot
reproduce".
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
On Tue, Jan 26, 2016 at 12:41 PM, Manfred Bergmann
wrote:
> Thanks for all your efforts.
>
> I think t
Hi.
Thank you a lot for answering.
Your suggestion helped me in solving the problem .
I also had to add an injection call in the WicketApplication getter, as
follows:
public static WicketApplication get() {
Application application = Application.get();
Injector.get().inject(application);
Glad it works now!
Better move Injector.get().inject(application); to the constructor of
YourWicketApplication: Injector.get().inject(this);
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
On Tue, Jan 26, 2016 at 3:00 PM, MM_at_ANO wrote:
> Hi.
>
> Thank you a l
Is anybody planning any Wicket presentations at ApacheCon North America
in May?
--
Jered
