Thank you martin.
let me upgrade to wicket 7.x. it may resolve.
On Mon, Sep 12, 2016 at 11:33 AM, Martin Grigorov
wrote:
> On Mon, Sep 12, 2016 at 5:26 PM, durairaj t
> wrote:
>
> > Hi Martin,
> >
> > DefaultPageStore#storePage(SerializedPage
On Mon, Sep 12, 2016 at 5:26 PM, durairaj t wrote:
> Hi Martin,
>
> DefaultPageStore#storePage(SerializedPage page) is holding only 40 pages
> in
> cache and removes others. It seems pageSotre appending every new versions
> and deleting old one. Like, cache.remove(0).
>
Hi Martin,
DefaultPageStore#storePage(SerializedPage page) is holding only 40 pages in
cache and removes others. It seems pageSotre appending every new versions
and deleting old one. Like, cache.remove(0).
I'm keeping my page in session and trying to fetch from session . But
wicket looking into
Hi,
On Thu, Sep 8, 2016 at 8:38 PM, durairaj t wrote:
> I have added the below code in my WebApp.java to keep the pages in session
> alive. Is it correct? Any help?
>
> setPageManagerProvider(new DefaultPageManagerProvider(this)
> {
> protected IDataStore
I have added the below code in my WebApp.java to keep the pages in session
alive. Is it correct? Any help?
setPageManagerProvider(new DefaultPageManagerProvider(this)
{
protected IDataStore newDataStore()
{
//new HttpSessionDataStore(getPageManagerContext(), new
Hi Martin,
I got the exact error message while debugging in eclipse;
*Error*: " org.apache.wicket.protocol.http.PageExpiredException: Page with
id '3' has expired."
I tried following code snippet in the page constructor. It seems the
following code updating the page until I'm moving out from
Thank you martin! Let me try this.
On Wed, Aug 31, 2016 at 2:27 PM, Martin Grigorov
wrote:
> Hi,
>
> Put a breakpoint at RequestCycle#setResponsePage(Class, PageParameters)
> and
> see who and why is calling it. This will tell you the reason.
> If this doesn't help then
Hi,
Put a breakpoint at RequestCycle#setResponsePage(Class, PageParameters) and
see who and why is calling it. This will tell you the reason.
If this doesn't help then put breakpoints in
RestartReponseAtInterceptPageException constructors.
Martin Grigorov
Wicket Training and Consulting
I got the same issue in Wicket 1.5, so I migrated it to 6.23, but still it
is happening.
Moreover, I used "*Session.get().replaceSession()**;*" just to reproduce
the issue. it will not be in the actual application code.
and I just used "* WebSession.get().clear(); *, *Session.get().clear(); , *
Javadoc from Session # replaceSession() says : Call() upon login to protect
against session fixation.
Until Wicket version 6.21 the destroy method did not set the session id to null.
In 6.23, Session # destroy() set session#id to null, this is why Login Page is
loaded.
Hope this helps
Thank you for your quick response.
*Session:* 30 minutes.
*Html Header:*
http://www.w3.org/TR/html4/loose.dtd;>
http://wicket.apache.org;>
-
-
Hi,
What is the session-timeout ?
Can you show the html page header ? and any java code that modify it.
François
> Le 31 août 2016 à 15:49, durairaj t a écrit :
>
> I'm migrating to wicket 6.23, createPage() is working as expected in many
> modules, but not in the
I'm migrating to wicket 6.23, createPage() is working as expected in many
modules, but not in the below scenario.
There is a search modal window in the application, which is used to search
data and keep the entire Page in session to retrieve the data back from the
session (for the Back button
13 matches
Mail list logo