Sure! But it doesn't help. And as I said, there is no error in my logs,
neither client-side nor server-side.
As I understand things, it should work with any version of Atmosphere
starting from 1.0.0, right?
Do you have any clue?
Regards,
Pierre
On Thu, Jan 10, 2013 at 1:07 PM, Emond
Yes, it should work with any 1.0 version. I think you should try to verify the
AJAX-messges, perhaps with Wicket's AJAX-debugger.
Best regards,
Emond
On Friday 11 January 2013 17:06:09 Pierre Goupil wrote:
Sure! But it doesn't help. And as I said, there is no error in my logs,
neither
I've found it! I had a HttpSession supported: false in my start-up Tomcat
logs when using Atmosphere 1.0.5. I don't know why, but I assume it's a
default behaviour change because when using Atmosphere 1.0.0 and changing
nothing else, I had: HttpSession supported: true. So I've followed
That's good to hear. I totally forgot about that option. It was added some
time ago and is indeed needed for Wicket. Without it the behavior does not
work because it is stateful.
Best regards,
Emond
Op 11 jan. 2013 19:01 schreef Pierre Goupil goupilpie...@gmail.com het
volgende:
I've found it!
With recent versions of wicket-atmosphere, you are required to add this
parameter to the AtmosphereServlet:
init-param
param-nameorg.atmosphere.cpr.broadcastFilterClasses/param-name
param-valueorg.apache.wicket.atmosphere.TrackMessageSizeFilter/param-
value
/init-param
Did you
