Thank you Martin for your help and guidance. It was our Login Page that was
using Form component instead of StatelessForm that was leading this session
data creation problem in our application.
What I have found that To make a page Stateless ( as the login pages should
be stateless) we have to
On Fri, Feb 22, 2019 at 4:02 AM kyc wrote:
> I applied the SessionPerTabHttpSessionStore and SessionPerTabBehavior (by
> adding cookie to session storage) in our site (ref. to
> https://issues.apache.org/jira/browse/WICKET-6358
> https://github.com/martin-g/blogs/tree/master/session-per-tab
>
LoginPage(Page).onBeforeRender() line: 808
Does it mean the Page.class 808 ?
Page.class line 808 : getSession().bind();
/**
*
* @see org.apache.wicket.Component#onBeforeRender()
*/
@Override
protected void onBeforeRender()
{
I applied the SessionPerTabHttpSessionStore and SessionPerTabBehavior (by
adding cookie to session storage) in our site (ref. to
https://issues.apache.org/jira/browse/WICKET-6358
https://github.com/martin-g/blogs/tree/master/session-per-tab
which causes the stateless login page creates new
The stacktrace says: LoginPage(Page).onBeforeRender() line: 808
What is the code at lines 800-808 in your LoginPage class ?
On Thu, Feb 21, 2019 at 11:56 AM kyc wrote:
> After logout page, it will redirect to the login page. I have already
> converted the login and logout pages to Stateless
After logout page, it will redirect to the login page. I have already
converted the login and logout pages to Stateless page by adding
@StatelessComponent with the StatelessChecker to them (without exception in
runtime). I don't know why the bind() is still being called and new session
is
Hi,
The question is what leads to the call of Session#bind().
While the debugger is at Session#bind() see what is the stacktrace from top
to bottom.
Maybe after logout you redirect to a stateful page and Wicket needs to
create a new Session to store that page ...
On Thu, Feb 21, 2019 at 10:21 AM
As I encountered the same problem as AliKhan, I follow Martin's suggestion
to upgrade the wicket version from 7.10 to 7.12. However, I still go to the
following code inside the bind() method when the session is invalidate.
// explicitly create a session
While the debugger is stopped at the breakpoint you can see what leads to
this call in the stacktrace.
If it is coming from the application code then you should fix it.
If it is triggered by Wicket itself then please upgrade to 7.12.0 and try
again. If it still does the same then please create a
Thanks for your quick reply!
I have verified as you suggested to breakpoint at Session#bind(). This
method is called 2 times after the session is invalidated. Strange thing is
that when user login, bind() is called only 1 time but on session invalidate
it is being called 2 times.
I did not
Hi,
Please update Wicket to a newer version! E.g. 7.12.0
If this doesn't help then put a breakpoint at
org.apache.wicket.Session#bind() method and see whether it is called after
the invalidation of the previous session.
It seems something leads to a new creation of an http session.
On Wed, Feb
11 matches
Mail list logo
