Martin Grigorov
> Wicket Training and Consulting
> https://twitter.com/mtgrigorov
>
> On Thu, May 18, 2017 at 10:12 AM, Erwan Tanajaya <r_...@yahoo.com.invalid>
> wrote:
>
>> hi all,
>> I have problem always get Page Expired error(event i set my session
>&g
igorov
On Thu, May 18, 2017 at 10:12 AM, Erwan Tanajaya <r_...@yahoo.com.invalid>
wrote:
> hi all,
> I have problem always get Page Expired error(event i set my session
> expired time to 8 hour), it happen if i open a page that had a datatable
> with have hundred of row.If i
ed at all.
>
> Martin Grigorov
> Wicket Training and Consulting
> https://twitter.com/mtgrigorov
>
> On Thu, May 18, 2017 at 10:12 AM, Erwan Tanajaya <r_...@yahoo.com.invalid>
> wrote:
>
>> hi all,
>> I have problem always get Page Expired error(event i
;r_...@yahoo.com.invalid>
wrote:
> hi all,
> I have problem always get Page Expired error(event i set my session
> expired time to 8 hour), it happen if i open a page that had a datatable
> with have hundred of row.If i click a button that had a setResponsePage to
> a new page when the page is
limit displayed
rows to some reasonable count?
Or block page navigations until data will be fully available?
On Thu, May 18, 2017 at 3:12 PM, Erwan Tanajaya <r_...@yahoo.com.invalid> wrote:
> hi all,
> I have problem always get Page Expired error(event i set my session expired
> time
Maybe it worth to add paging and limit displayed rows to some reasonable count?
Or block page navigations until data will be fully available?
On Thu, May 18, 2017 at 3:12 PM, Erwan Tanajaya <r_...@yahoo.com.invalid> wrote:
> hi all,
> I have problem always get Page Expired error(ev
hi all,
I have problem always get Page Expired error(event i set my session expired
time to 8 hour), it happen if i open a page that had a datatable with have
hundred of row.If i click a button that had a setResponsePage to a new page
when the page is still loading and do something in the new
wicket to 6.18.0, I got page expired exception page and the
url became plaintext after I redirect it to another page.
Any suggestions?
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail
Dear all
I wrote an openid provider web application with 6.14.0 (upgrade from 1.5.3
gradually) which enabled ssl and url encryption. Everything worked fine
until I upgrade wicket to 6.18.0, I got page expired exception page and the
url became plaintext after I redirect it to another page.
Any
tab. (yeah, i know it took me 4 months to get back to this but i
was busy. :-) )
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Bunch-of-Page-Expired-exceptions-in-Wicket-6-10-0-tp4661502p4663946.html
Sent from the Users forum mailing list archive at Nabble.com
My next step to solve this problem was to run some tests with The Grinder
Load Testing Tool.
A nice tool, but I got the same problem than in JMeter - Page Expired!
I use the Cookie Manager and tried also URL Rewriting (attaching the
jsessionid to each url) but without
success.
The problem occurs
I'm using Wicket 1.5.8 and tried to use JMeter for loading tests.
My problem is that it records well but when running the recorded scenario I
get a page expired response.
It occurs also when I run only one thread one time.
Yes, I use HTTP Cookie Manager and delete session after each run.
I know
makes me think that going off the HttpSessionListener might
be better.
~ Thank you,
Paul Bors
-Original Message-
From: Martin Grigorov [mailto:mgrigo...@apache.org]
Sent: Saturday, September 28, 2013 3:44 AM
To: users@wicket.apache.org
Subject: Re: Bunch of Page Expired exceptions
Subject: Re: Bunch of Page Expired exceptions in Wicket 6.10.0 (GlassFish
v3 and v4)
I think both suggestions should be applied.
The intentions are more clear, IMO.
But let's wait Paul to explain what problem he faced. I don't expect
problems with session timeouts because this is managed by the web
, September 28, 2013 3:44 AM
To: users@wicket.apache.org
Subject: Re: Bunch of Page Expired exceptions in Wicket 6.10.0
(GlassFish v3 and v4)
I think both suggestions should be applied.
The intentions are more clear, IMO.
But let's wait Paul to explain what problem he faced. I don't expect
problems
,
Paul Bors
-Original Message-
From: Martin Grigorov [mailto:mgrigo...@apache.org]
Sent: Saturday, September 28, 2013 3:44 AM
To: users@wicket.apache.org
Subject: Re: Bunch of Page Expired exceptions in Wicket 6.10.0
(GlassFish v3 and v4)
I think both suggestions should be applied
@wicket.apache.org
Subject: Re: Bunch of Page Expired exceptions in Wicket 6.10.0
(GlassFish v3 and v4)
I think both suggestions should be applied.
The intentions are more clear, IMO.
But let's wait Paul to explain what problem he faced. I don't expect
problems with session timeouts because
of Page Expired exceptions in Wicket 6.10.0 (GlassFish v3
and v4)
https://issues.apache.org/jira/browse/WICKET-5380
On Mon, Sep 30, 2013 at 12:32 PM, Martin Grigorov mgrigo...@apache.orgwrote:
Applying only the first change that I suggested works on all - Jetty
8, Tomcat 7 and Glassfish 4
implementation breaks the session timeout.
~ Thank you,
Paul Bors
-Original Message-
From: Paul Bors [mailto:p...@bors.ws]
Sent: Friday, September 27, 2013 5:51 PM
To: users@wicket.apache.org
Cc: d...@wicket.apache.org
Subject: RE: Bunch of Page Expired exceptions in Wicket 6.10.0 (GlassFish v3
: Friday, September 27, 2013 5:51 PM
To: users@wicket.apache.org
Cc: d...@wicket.apache.org
Subject: RE: Bunch of Page Expired exceptions in Wicket 6.10.0 (GlassFish
v3 and v4)
I tested with the proposed o.a.w.p.PageStoreManager.**
PersistentRequestAdapter#**getSessionEntry() new implementation
-Original Message-
From: Martin Grigorov [mailto:mgrigo...@apache.org]
Sent: Saturday, September 28, 2013 3:44 AM
To: users@wicket.apache.org
Subject: Re: Bunch of Page Expired exceptions in Wicket 6.10.0 (GlassFish v3
and v4)
I think both suggestions should be applied.
The intentions are more
/Bunch-of-Page-Expired-exceptions-in-Wicket-6-10-0-tp4661502p4661540.html
Sent from the Users forum mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users
.
This is not correct.
Browser tabs share the same http session.
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Bunch-of-Page-Expired-exceptions-in-Wicket-6-10-0-tp4661502p4661540.html
Sent from the Users forum mailing list archive at Nabble.com
-
From: Martin Grigorov [mailto:mgrigo...@apache.org]
Sent: Thursday, September 26, 2013 5:01 PM
To: users@wicket.apache.org
Cc: Sven Meier
Subject: Re: Bunch of Page Expired exceptions in Wicket 6.10.0
The problem seems to be caused by
http://issues.apache.org/jira/browse/WICKET-5164
With this change
,
Paul Bors
-Original Message-
From: Martin Grigorov [mailto:mgrigo...@apache.org]
Sent: Thursday, September 26, 2013 5:01 PM
To: users@wicket.apache.org
Cc: Sven Meier
Subject: Re: Bunch of Page Expired exceptions in Wicket 6.10.0
The problem seems to be caused by
http
: Bunch of Page Expired exceptions in Wicket 6.10.0
The problem seems to be caused by
http://issues.apache.org/jira/**browse/WICKET-5164http://issues.apache.org/jira/browse/WICKET-5164
With this change any kind of attribute added to the http session causes
total removal of all data from the disk store
: Sven Meier
Subject: Re: Bunch of Page Expired exceptions in Wicket 6.10.0
The problem seems to be caused by
http://issues.apache.org/jira/browse/WICKET-5164http://issues.apache.org/jira/**browse/WICKET-5164
http://**issues.apache.org/jira/browse/**WICKET-5164http://issues.apache.org/jira
of Page Expired exceptions in Wicket 6.10.0
by tabs do you mean browser tabs?
if you have 2 tabs:
http://localhost:8080/Foo
and
http://localhost:8081/Bar
then reloading each tab will often invalidate the previous tab. the session
cookie is overwritten.
--
View this message in context:
http
Message-
From: Martin Grigorov [mailto:mgrigo...@apache.org]
Sent: Friday, September 27, 2013 10:09 AM
To: users@wicket.apache.org
Subject: Re: Bunch of Page Expired exceptions in Wicket 6.10.0
I created a simple app and tested it on these 3 servers + Jetty 8.1.13.
The app shows that SessionEntry
,
but that'll really be a nice to have at this point.
~ Thank you,
Paul Bors
-Original Message-
From: Paul Bors [mailto:p...@bors.ws]
Sent: Friday, September 27, 2013 11:04 AM
To: users@wicket.apache.org
Subject: RE: Bunch of Page Expired exceptions in Wicket 6.10.0
I so knew it! It also affects
://apache-wicket.1842946.n4.nabble.com/Bunch-of-Page-Expired-exceptions-in-Wicket-6-10-0-tp4661502p4661582.html
Sent from the Users forum mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr
,
p...@bors.ws
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Bunch-of-Page-Expired-exceptions-in-Wicket-6-10-0-tp4661502p4661582.html
Sent from the Users forum mailing list archive at Nabble.com
HttpSessionListener instead is
cleaner.
~ Thank you,
Paul Bors
-Original Message-
From: Martin Grigorov [mailto:mgrigo...@apache.org]
Sent: Friday, September 27, 2013 4:09 PM
To: users@wicket.apache.org
Cc: d...@wicket.apache.org
Subject: Re: Bunch of Page Expired exceptions in Wicket 6.10.0
I take that back, the new implementation breaks the session timeout.
~ Thank you,
Paul Bors
-Original Message-
From: Paul Bors [mailto:p...@bors.ws]
Sent: Friday, September 27, 2013 5:51 PM
To: users@wicket.apache.org
Cc: d...@wicket.apache.org
Subject: RE: Bunch of Page Expired
On Sep 25, 2013, at 5:59 PM, Paul Bors p...@bors.ws wrote:
Hey guys,
Just wondering what could be the cause of the many page expired
exceptions I am running into with this webapp whenever the user changes
tabs and then selects the browser’s “Back” button or whenever the user
downloads
:201)
at
org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:282)
This happens for each page request and as soon as a form is submitted the back
button redirects the user to the page expired for good reason (page store is
empty).
I also noticed
to the page expired for good reason (page
store is empty).
I also noticed that the work done for WICKET-3865 is not registering the
DebugPageManagerProvider which I added inside my init’s method via:
setPageManagerProvider(new
DebugPageManagerProvider(WicketApplication.this));
Please
:)
~ Thank you,
Paul Bors
-Original Message-
From: Martin Grigorov [mailto:mgrigo...@apache.org]
Sent: Thursday, September 26, 2013 5:01 PM
To: users@wicket.apache.org
Cc: Sven Meier
Subject: Re: Bunch of Page Expired exceptions in Wicket 6.10.0
The problem seems to be caused by
http
Hey guys,
Just wondering what could be the cause of the many page expired exceptions I
am running into with this webapp whenever the user changes tabs and then
selects the browser's Back button or whenever the user downloads a
resource via a button and the form is being submitted a second time
, 2013, at 5:59 PM, Paul Bors p...@bors.ws wrote:
Hey guys,
Just wondering what could be the cause of the many page expired exceptions I
am running into with this webapp whenever the user changes tabs and then
selects the browser’s “Back” button or whenever the user downloads a resource
...@yahoo.dewrote:
When I try to close the ModalWindow with window.close(target)
I get the error Page expired
How can I solve this ?
--**--**-
To unsubscribe, e-mail:
users-unsubscribe@wicket.**apache.orgusers-unsubscr
When I try to close the ModalWindow with window.close(target)
I get the error Page expired
How can I solve this ?
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h
Hello *,
I have a DataTable with a column of clickable checkboxes. Each time the user
clicks a checkbox the server does some stuff on the database.
If the user clicks another checkbox before the server finished processing the
previous, he receives a Page Expired error. The behaviour
the previous, he receives a Page Expired error. The behaviour is
understandable, since the user obviously clicked a checkbox that was on a
page that was being recreated, however I don't know how to avoid or
workaround the problem.
I've partially solved the problem: it was being caused by an anonymous
Hi,
is there a way to have different page expiry error pages? For my app I
would like to redirect browsing users (not logged in) to a real error
page which is plain and simple but logged in users should be redirected
to the login page on session timeout.
Thanks,
Karsten
Hi,
See org.apache.wicket.request.cycle.AbstractRequestCycleListener#onException
With this you can return RenderPageRequestHanlder specific for any type of
exception.
On Mon, Dec 10, 2012 at 11:37 AM, Karsten Gaul karsten.g...@exedio.comwrote:
Hi,
is there a way to have different page
Hi,
and sorry. Forgot to mention that I'm using wicket 1.4.21 so I was
trying to override
AbstractRequestCycleProcessor#respond(RuntimeException e, RequestCycle
requestCycle) and on second thought I guess overriding
RequestCycle#onRuntimeException should do the trick. I'll give it a try.
. The PagingNavigator shows 6
links for 10 entries per page. But after clicking on one of the links, the
objects
from the getResults() class are empty.
Any idea?
Andre
- Original Message -
From: b...@iswd.nl
To: users@wicket.apache.org
Date: 11.04.2012 00:51:38
Subject: Re: Page Expired
clicking on one of the
links, the objects
from the getResults() class are empty.
Any idea?
Andre
- Original Message -
From: b...@iswd.nl
To: users@wicket.apache.org
Date: 11.04.2012 00:51:38
Subject: Re: Page Expired with Google Analytics Tracking Code
per page. But after clicking on one of the links,
the objects
from the getResults() class are empty.
Any idea?
Andre
- Original Message -
From: b...@iswd.nl
To: users@wicket.apache.org
Date: 11.04.2012 00:51:38
Subject: Re: Page Expired with Google Analytics Tracking
:38
Subject: Re: Page Expired with Google Analytics Tracking Code
Hi,
It sounds a lot like you are not using models properly. E.g. your
results method parameter has a length which overflows the page size
(and thus the pagingnavigator renders page links), but on a second
request
- Original Message -
From: b...@iswd.nl
To: users@wicket.apache.org
Date: 11.04.2012 00:51:38
Subject: Re: Page Expired with Google Analytics Tracking Code
Hi,
It sounds a lot like you are not using models properly. E.g. your
results method parameter has a length which overflows the page size
links for 10 entries per page. But after clicking on one of the links, the
objects
from the getResults() class are empty.
Any idea?
Andre
- Original Message -
From: b...@iswd.nl
To: users@wicket.apache.org
Date: 11.04.2012 00:51:38
Subject: Re: Page Expired with Google Analytics Tracking
: Re: Page Expired with Google Analytics Tracking Code
Hi,
It sounds a lot like you are not using models properly. E.g. your
results method parameter has a length which overflows the page size
(and thus the pagingnavigator renders page links), but on a second
request the contents
: Page Expired with Google Analytics Tracking Code
Hi,
It sounds a lot like you are not using models properly. E.g. your
results method parameter has a length which overflows the page size
(and thus the pagingnavigator renders page links), but on a second
request the contents of results are null
00:51:38
Subject: Re: Page Expired with Google Analytics Tracking Code
Hi,
It sounds a lot like you are not using models properly. E.g. your
results method parameter has a length which overflows the page size
(and thus the pagingnavigator renders page links), but on a second
localize the following error:
page expired:
http://localhost:8080/wicket/page?7-1.IFormSubmitListener-resultsContent-searchPanel-searchForm
This means. The error occurs, when I make another search via my
search form which is a normal Form with a textfield and a submit
button
.
Bas
Op 7-4-2012 14:04, schreef Andre Schütz:
Hi,
I tested the page and could localize the following error:
page expired:
http://localhost:8080/wicket/page?7-1.IFormSubmitListener-resultsContent-searchPanel-searchForm
This means. The error occurs, when I make another search via my
search form
,
No, we have been using the tracking code for years with wicket (1.3, 1.4
and 1.5) with 0 issues.
I'm certain your Page expired error is caused by something else.
From your description it sounds like your search results page is
stateful, but no longer available when you perform
Hi,
I tested the page and could localize the following error:
page expired:
http://localhost:8080/wicket/page?7-1.IFormSubmitListener-resultsContent-searchPanel-searchForm
This means. The error occurs, when I make another search via my
search form which is a normal Form with a textfield
for the cause of your PageExpiredException.
Bas
Op 7-4-2012 14:04, schreef Andre Schütz:
Hi,
I tested the page and could localize the following error:
page expired:
http://localhost:8080/wicket/page?7-1.IFormSubmitListener-resultsContent-searchPanel-searchForm
This means. The error occurs, when I make
Op 7-4-2012 14:04, schreef Andre Schütz:
Hi,
I tested the page and could localize the following error:
page expired:
http://localhost:8080/wicket/page?7-1.IFormSubmitListener-resultsContent-searchPanel-searchForm
This means. The error occurs, when I make another search via my
PageExpiredException.
Bas
Op 7-4-2012 14:04, schreef Andre Schütz:
Hi,
I tested the page and could localize the following error:
page expired:
http://localhost:8080/wicket/page?7-1.IFormSubmitListener-resultsContent-searchPanel-searchForm
This means. The error occurs, when I make another search via my
is presented
We do:
Page 1 - search for something
Page 2 appears and shows search progress
Page 3 appears and displays the results
Page 3 has a search box and we start another search
-- Page expired error
Any ideas why this happens and how we can stop that?
Thanks,
Andre
--
Andre Schütz
Hi Andre,
No, we have been using the tracking code for years with wicket (1.3, 1.4
and 1.5) with 0 issues.
I'm certain your Page expired error is caused by something else.
From your description it sounds like your search results page is
stateful, but no longer available when you perform
is done
Page 3 is the result page, where the search result is presented
We do:
Page 1 - search for something
Page 2 appears and shows search progress
Page 3 appears and displays the results
Page 3 has a search box and we start another search
-- Page expired error
Any ideas why this happens and how we
/AjaxSelfUpdatingBehavior-page-expired-tp4470925p4471087.html
Sent from the Users forum mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h
I am using a tab panel...
On one tab I added an AjaxSelfUpdatingBehavior because I want the contents
of the panel to refresh periodically.
When I switch away from that tab to another tab, I get 'page expired' ...
what am I doing wrong?
TIA
--
View this message in context:
http://apache-wicket
hi again
Can you help me with this? I'm really stuck with this problem...
thanks
Rebecca
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/double-click-on-AjaxSubmitLink-and-page-expired-tp4449450p4453153.html
Sent from the Users forum mailing list archive
-on-AjaxSubmitLink-and-page-expired-tp4449450p4453153.html
Sent from the Users forum mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h
CharSequence decorateOnFailureScript(CharSequence script) {
return reset + script;
}
}
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/double-click-on-AjaxSubmitLink-and-page-expired-tp4449450p4453255.html
Sent from the Users forum mailing list archive at Nabble.com
decorateOnFailureScript(CharSequence script) {
return reset + script;
}
}
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/double-click-on-AjaxSubmitLink-and-page-expired-tp4449450p4453255.html
Sent from the Users forum mailing list archive at Nabble.com
in onSubmit of the AjaxSubmitLink i do:
getSession.untouch(firstPage);
getSession.clear();
setResponsePaeg(new myNextPage());
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/double-click-on-AjaxSubmitLink-and-page-expired-tp4449450p4453399.html
Sent from the Users
:
in onSubmit of the AjaxSubmitLink i do:
getSession.untouch(firstPage);
getSession.clear();
setResponsePaeg(new myNextPage());
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/double-click-on-AjaxSubmitLink-and-page-expired-tp4449450p4453399.html
Sent from the Users
I already tried removing the reset code - didn't work.
By veil you mean something like the jquery plugin blockUi?
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/double-click-on-AjaxSubmitLink-and-page-expired-tp4449450p4453452.html
Sent from the Users forum mailing
-wicket.1842946.n4.nabble.com/double-click-on-AjaxSubmitLink-and-page-expired-tp4449450p4453452.html
Sent from the Users forum mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
thanks Martin - I'll try the veil and report later
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/double-click-on-AjaxSubmitLink-and-page-expired-tp4449450p4453493.html
Sent from the Users forum mailing list archive at Nabble.com
this in order to prevent the user from returning to this page.
The problem is when the user clicks twice on the AjaxSubmitLink - the clear
session logic get's called in the first click and then i get page expired
in the second link.
I tried to use AjaxCallDecorator to block the button in the second click
sorry - i forgot - I'm using wicket 1.4.18
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/double-click-on-AjaxSubmitLink-and-page-expired-tp4449450p4449457.html
Sent from the Users forum mailing list archive at Nabble.com
1.4.18
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/double-click-on-AjaxSubmitLink-and-page-expired-tp4449450p4449457.html
Sent from the Users forum mailing list archive at Nabble.com
forgot - I'm using wicket 1.4.18
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/double-click-on-AjaxSubmitLink-and-page-expired-tp4449450p4449457.html
Sent from the Users forum mailing list archive at Nabble.com
worked
for me and i saw other similar posts in this forum, where other wicket users
used the same hack. I'll be glad to use a better solution.
thanks
Rebecca
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/double-click-on-AjaxSubmitLink-and-page-expired-tp4449450p4449825
/wicket/wicket/**bookmarkable/com.mni.**
SignInPage?1
http://192.168.33.20:9002/rems/wicket/wicket/bookmarkable/com.mni.SignInPage?1
*Default PageExpiredErrorPage behavior*
After there is a page timeout and the /default /page-expired error
page
opens, the Return to home page button
page. (That is how the button on the default page-expired error
page works.)
When the user first opens the web site, whether with the default or the
custom page-expired page, they see a log in page with URL
http://mydomain.com/rems/wicket/wicket/bookmarkable/com.mni.SignInPage?1.
Here
to the home page. Since we're using authorization the
user first goes to the login page so they can log in before going to the
home page. (That is how the button on the default page-expired error page
works.)
When the user first opens the web site, whether with the default or the
custom page-expired
and goes to the home page. Since we're using authorization the
user first goes to the login page so they can log in before going to the
home page. (That is how the button on the default page-expired error page
works.)
When the user first opens the web site, whether with the default or the
custom page
to
home page and goes to the home page. Since we're using authorization the
user first goes to the login page so they can log in before going to the
home page. (That is how the button on the default page-expired error page
works.)
When the user first opens the web site, whether with the default
to the login page so they can log in (similar to the button
on the default page-expired error page). /
/
When the user first opens the web site, they see a log in page with URL
/http://mydomain.com/rems/**wicket/wicket/bookmarkable/**
com.mni.SignInPage?1/http://mydomain.com/rems/wicket/wicket
My apologies. I am reposting this without the distracting pseudo-formatting.
I created my own PageExpiredErrorPage. There is a button that is
supposed to take the user to the login page so they can log in (just
like the button on the default page-expired error page). /
/
When the user first
the user to the login page so they can log in (similar to the button
on the default page-expired error page). /
/
When the user first opens the web site, they see a log in page with URL
/http://mydomain.com/rems/**wicket/wicket/bookmarkable/**
com.mni.SignInPage?1/http://mydomain.com/rems/wicket
, Aug 26, 2011 at 1:27 AM, Scott Reedsr...@avacoda.com wrote:
A created my own PageExpiredErrorPage. There is a button that is supposed
to take the user to the login page so they can log in (similar to the
button
on the default page-expired error page). /
/
When the user first opens the web
in (similar to the
button
on the default page-expired error page). /
/
When the user first opens the web site, they see a log in page with URL
/http://mydomain.com/rems/**wicket/wicket/bookmarkable/**
com.mni.SignInPage?1/http://mydomain.com/rems/wicket/wicket/bookmarkable/com.mni.SignInPage
I found that replacing add(linkHomePage( homeLink )) with my code
below works. Can anyone explain?
Thanks,
Scorr
void addHomeBtn( String id, MarkupContainer parent, final WebPage page )
{
final AbstractDefaultAjaxBehavior homeBehavior = new
AbstractDefaultAjaxBehavior()
{
...@avacoda.com wrote:
A created my own PageExpiredErrorPage. There is a button that is supposed
to take the user to the login page so they can log in (similar to the
button
on the default page-expired error page). /
/
When the user first opens the web site, they see a log in page with URL
/http
that is
supposed
to take the user to the login page so they can log in (similar to the
button
on the default page-expired error page). /
/
When the user first opens the web site, they see a log in page with
URL
/http://mydomain.com/rems/**wicket/wicket/bookmarkable/**
com.mni.SignInPage?1
A created my own PageExpiredErrorPage. There is a button that is
supposed to take the user to the login page so they can log in (similar
to the button on the default page-expired error page). /
/
When the user first opens the web site, they see a log in page with URL
/http://mydomain.com/rems
Hi,
Upgrading wicket from 1.5-RC4.2 to 1.5-RC5.1 make my Junit Test down
with the error 'Page expired'
/**
* Simple test using the WicketTester
*/
public class TestHomePage
{
private WicketTester tester;
@Before
public void setUp()
{
tester = new WicketTester(new
,
Upgrading wicket from 1.5-RC4.2 to 1.5-RC5.1 make my Junit Test down with
the error 'Page expired'
/**
* Simple test using the WicketTester
*/
public class TestHomePage
{
private WicketTester tester;
@Before
public void setUp()
{
tester = new WicketTester(new
at 12:20 PM, Thomas Franconville
tfranconvi...@tetraedge.com wrote:
Hi,
Upgrading wicket from 1.5-RC4.2 to 1.5-RC5.1 make my Junit Test down with
the error 'Page expired'
/**
* Simple test using the WicketTester
*/
public class TestHomePage
{
private WicketTester tester;
@Before
with
the error 'Page expired'
/**
* Simple test using the WicketTester
*/
public class TestHomePage
{
private WicketTester tester;
@Before
public void setUp()
{
tester = new WicketTester(new MyApplication());
}
@Test
public void
1 - 100 of 300 matches
Mail list logo
