Hi,
There is nothing to configure in Wicket.
All you need is to make sure that your Wicket Session is bound (see
Session#bind() method). This will create a Http Session and save Wicket's
Session as attribute in it.
Usually it is recommended to use normal member variable in Wicket Session
instead
Thanks Francois,
I've been busy on another task. I'll look at the code soon.
Bruce
Sent from my iPad
On May 22, 2014, at 5:48 AM, Francois Meillet francois.meil...@gmail.com
wrote:
Hi Bruce,
This is just one solution :
Have a look at http://pastebin.com/03DF5pcw
François
Hi Martin,
thanks for the input. Using the wicket-native-websocket-javax 7.0.0-M1 in
conjunction with the 6.15.0 modules and configuring my embeded jetty correctly
( :-) ) I got it to work.
jan
- Original Message -
From: Martin Grigorov mgrigo...@apache.org
To:
Hi Jan,
The problem is that Jetty 9.1 (and any JSR356 impl) is built with Java 7 so
it cannot be part of Wicket 6.
But maybe it is not such a big problem - Jetty 9.0 is also built with Java
7.
Feel free to file a ticket if you want -javax module to be downported to
Wicket 6.x. It seems it works
Hi Martin,
Thank you for the suggestions.
I did manage to get the applications working together.
But... I'm not very sure if, what I am doing, is the correct way.
Therefor I created the minimal quickstart that does what I want it to do.
The quickstart is downloadable from: