; https://twitter.com/mtgrigorov
>
> On Thu, May 18, 2017 at 10:12 AM, Erwan Tanajaya
> 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 h
at 10:12 AM, Erwan Tanajaya
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 wh
tin Grigorov
> Wicket Training and Consulting
> https://twitter.com/mtgrigorov
>
> On Thu, May 18, 2017 at 10:12 AM, Erwan Tanajaya
> 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
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 somet
some reasonable count?
Or block page navigations until data will be fully available?
On Thu, May 18, 2017 at 3:12 PM, Erwan Tanajaya 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 datat
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 wrote:
> hi all,
> I have problem always get Page Expired error(event i set my session expired
>
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
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 wrote:
> Applying only the first change that I suggested works on all - Jetty
> 8, Tomcat 7 and Glassfish 4.
>
&g
etMaxInactiveInterval(sessionDuration);
>>>>>
>>>>> I set the session duration to 1 min and tried it with the new
>>>>> implementation for the getSessionEntry(), waited for a good 2-3 mins and
>>>>> the session is never invalidated any
er, unless
>>>> explicitly through the Logout button which calls
>>>> o.a.w.protocol.http.WebSession.get().invalidateNow();
>>>>
>>>> This is what makes me think that going off the HttpSessionListener
>>>> might be better.
>>>>
&
explicitly through the Logout button which calls
>>> o.a.w.protocol.http.WebSession.get().invalidateNow();
>>>
>>> This is what makes me think that going off the HttpSessionListener might
>>> be better.
>>>
>>> ~ Thank you,
>>> Paul Bors
&
t; ~ 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 in Wicket
ugh.
> >
> > @Paul: What is broken now?
> >
> > Sven
> >
> >
> > On 09/28/2013 12:15 AM, Paul Bors wrote:
> >
> >> I take that back, the new implementation breaks the session timeout.
> >>
> >> ~ Thank you,
> >>Pa
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.
The intention
ul 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 Wicke
k, 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 exceptions in Wicket 6.10.0 (Gl
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
n of using 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 Wic
x27;s see what becomes of this...
>
>
>
> -
> ~ Thank you,
> p...@bors.ws
> --
> View this message in context:
> http://apache-wicket.1842946.n4.nabble.com/Bunch-of-Page-Expired-exceptions-in-Wicket-6-10
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.
-
To unsubscribe, e-mail:
just the private 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 Wick
--Original 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 Se
ch 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:
;> On 09/26/2013 11:46 PM, Paul Bors wrote:
>>>
>>> By rolling back to Wicket 6.9.0 I can confirm that the PageStoreManager
>>>> works and I do see my page store content via DiskStoreBrowserPage.
>>>>
>>>> For a bit more environmental details, I was
apache.wicket.protocol.**http.WicketFilter.doFilter(**
WicketFilter.jav
a: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 that the work done for WICKET-3865 is
nvironmental details, I was running my tests on top of
>> GlassFish 3.1.2.2
>>
>> Thanks for the heads up Martin!
>> For now I'll stick to 6.9.x :)
>>
>> ~ Thank you,
>>Paul Bors
>>
>> -Original Message-
>> From: Marti
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://issues.apache.org/jira/browse/WICKET-5164
With thi
ookie is overwritten.
>
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
>
/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
6.9.x :)
~ 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
at
> org.apache.wicket.request.cycle.RequestCycle.onDetach(RequestCycle.java:640)
>
> at
> org.apache.wicket.request.cycle.RequestCycle.detach(RequestCycle.java:589)
>
> at
> org.apache.wicket.request.cycle.RequestCycle.processRequestAndDetach(Reque
tFilter.processRequest(WicketFilter.java: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 s
; Stay tuned... ;)
>
> Have a great day,
> Paul Bors
>
> > On Sep 25, 2013, at 5:59 PM, Paul Bors wrote:
> >
> > Hey guys,
> >
> > Just wondering what could be the cause of the many page expired
> exceptions I am running into with this webapp whenever th
n Sep 25, 2013, at 5:59 PM, Paul Bors 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 d
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 sub
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.org
> For additional c
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
inished processing
> 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 solve
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 is
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.
Th
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 wrote:
> Hi,
>
> is there a way to have different page expiry error pages? For my
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
That's the reason why I said it is "not completely empty".
I know that there are 60 results to display. 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
- Or
gt;>>> @Override
> > >>>> protected void onAjaxEvent(AjaxRequestTarget target) {
> > >>>> super.onAjaxEvent(target);
> > >>>> target.appendJavaScript("scrollTo(0,0)");
> &g
>>>>
> >>>>
> >>>>
> >>>>
> >>>> Op 11-4-2012 11:22, schreef wic...@faustas.de:
> >>>>> Hi,
> >>>>>
> >>>>> thank you for the answer.
> >>>>>
> >>
e. 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 Code
Hi,
It sounds a lot l
I access with getResults() and getTime().
> >>> The content of the getResults() variable is a class that implements the
> >>> Serializable
> >>> interface. The getTime() variable just has a Vector with time strings.
> >>>
> >>> Now comes th
why I said it is "not completely empty".
I know that there are 60 results to display. 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 -
page reload and once again empty after clicking
> > on one of the links from the PagingNavigator.
> > That's the reason why I said it is "not completely empty".
> >
> > I know that there are 60 results to display. The PagingNavigator shows 6
> > links
Navigator.
That's the reason why I said it is "not completely empty".
I know that there are 60 results to display. 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
-
.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
> (and thus the pagingnaviga
re you are looking in
the right place 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
lation) if the google analytics code (or the component you've wrapped
> > >> it in) is really the issue you are facing.
> > >>
> > >> You say that everything works ok when you add the query parameter for
> > >> the search. Having that parameter mea
> >> stateful url. (The /wicket/page start of the url indicates a stateful
> >> page).
> >>
> >> But please start with steps 1-4 above to make sure you are looking in
> >> the right place for the cause of your PageExpiredException.
> >>
> >>
xpiredException.
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
re looking in
> the right place 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:/
t place 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 occu
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 and
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 whe
re 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 happe
one
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 a
/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://apa
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 Nabbl
> http://apache-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-u
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 User
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-tp4449450p445339
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
;
> }
>
> public CharSequence decorateOnSuccessScript(CharSequence script) {
> return reset + script;
> }
> public CharSequence decorateOnFailureScript(CharSequence script) {
> return reset + script;
> }
> }
>
> --
> View this message in context:
> http://ap
rSequence decorateOnSuccessScript(CharSequence script) {
return reset + script;
}
public 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-
.com/double-click-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
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 archi
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-tp4449450p44
e:
>
>> 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-tp444
--
> 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.
>
> -
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 Nabbl
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 t
gt;>
>>> I created my own PageExpiredErrorPage with a button that says "Return 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 p
ome 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 defa
; 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 wit
e 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 page, they see a log in page with URL
http://mydomain.com/rems/wicket/wicket/bookmarkable/com.mni.SignI
t;> >>>> Make that change and try again.
>> >>>>
>> >>>> *Bruno Borges*
>> >>>> (21) 7672-7099
>> >>>> *www.brunoborges.com*
>> >>>>
>> >>>>
>> >>>>
>> &g
t;>
> >>>> Make that change and try again.
> >>>>
> >>>> *Bruno Borges*
> >>>> (21) 7672-7099
> >>>> *www.brunoborges.com*
> >>>>
> >>>>
> >>>>
> >>>> On Fri, Aug 26, 2011
t;
>>>> Make that change and try again.
>>>>
>>>> *Bruno Borges*
>>>> (21) 7672-7099
>>>> *www.brunoborges.com*
>>>>
>>>>
>>>>
>>>> On Fri, Aug 26, 2011 at 1:27 AM, Scott Reed wrote:
>>&g
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()
{
;>> On Fri, Aug 26, 2011 at 1:27 AM, Scott Reed 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 th
again.
>>
>> *Bruno Borges*
>> (21) 7672-7099
>> *www.brunoborges.com*
>>
>>
>>
>> On Fri, Aug 26, 2011 at 1:27 AM, Scott Reed wrote:
>>
>>> A created my own PageExpiredErrorPage. There is a button that is supposed
>>> to take t
posed
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/<http://myd
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
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://mydomai
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
t;>>
>>> 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
&g
at 12:20 PM, Thomas Franconville
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
public
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()
>
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 Wicket
1 - 100 of 307 matches
Mail list logo
