CODEWITHSUNDEEP
javaajaxsessionwickettabbed-browsing
Rob Audenaerde
Rob Audenaerde

Reputation: 20029

Wicket interaction between wicket-applications on localhost

I'm experiencing abnormal behaviour in ajax-related clicks in two Wicket Applications that both run on the same localhost on different ports (both served by Jetty)

I have two applications open in two tabs in Chrome. When I click on an AjaxLink in one of the applications, it sometimes works and sometimes does nothing (or something in the other Wicket tabs, as I see the tab title doing something).

This leads to undesired behaviour, as the links no longer work as required.

What can I do to prevent this interaction between tabs?

Upvotes: 1

Views: 113

Answers (1)

Rob Audenaerde
Rob Audenaerde

Reputation: 20029

I now use this:

this.getServletContext().getSessionCookieConfig().setName( applicationCookieName )

And change the applicationCookieName per application, that seems to prevent it.

It is probably caused by the JSESSIONID being shared by default, as can written in this answer: https://stackoverflow.com/a/5646933/461499

Upvotes: 0

Related Questions