> Thanks guys for all the help, you are amazingly responsive. Now I feel bad
> and have to be more responsive with open source project I manage 8-). You
> are setting the example!
Heh, cool. Which one is that?
> BTW, I came with solution after reading the first chapter of Wicket In
> Action.
And
I added:
setResponsePage(MyAppHome.class);
after session.invalidate();
, and that fixed the problem.
Thanks guys for all the help, you are amazingly responsive. Now I feel bad
and have to be more responsive with open source project I manage 8-). You
are setting the example!
BTW, I came with s
> After re-login when I get Page Expired, the url is:
> http://localhost:8080/MyApp/app/?wicket:interface=:0::
Yeah, that's a reference to an already rendered page. Try to find why
it tries to render that. You could try setting a break point in the
Wicket filter and go from there for instance, and
Oops, never mind. I see the new users list on Nabble. Just clicked on wrong
one. Sorry for the noise.
Eelco Hillenius wrote:
>
> Btw this user list is about to shut down. Please subscribe to
> [EMAIL PROTECTED] (by sending an email to
> [EMAIL PROTECTED]) and have future discussions there.
>
Thanks Eelco, I already did. But I like using Nabble so that is how I got to
this mailing list, and thought it is the new mailing list. Do you know if
[EMAIL PROTECTED] is available on Nabble?
Lubos
Eelco Hillenius wrote:
>
> Btw this user list is about to shut down. Please subscribe to
> [EM
After re-login when I get Page Expired, the url is:
http://localhost:8080/MyApp/app/?wicket:interface=:0::
igor.vaynberg wrote:
>
> hrm, i dont see how /MyApp/app can ever cause a page expired error because
> it is a bookmarkable url and so a new instance of page is always created.
> i
> would
Btw this user list is about to shut down. Please subscribe to
[EMAIL PROTECTED] (by sending an email to
[EMAIL PROTECTED]) and have future discussions there.
Eelco
-
This SF.net email is sponsored by: Splunk Inc.
Still greppi
> so you do not think that session.invalidate() can cause the page to expire?
Only if you try to render a page that is part of that old - now
invalidated - session. Make sure Wicket doesn't try to do that (e.g.
check whether the authorization strategy doesn't try to do another
redirect).
Eelco
-
Igor,
so you do not think that session.invalidate() can cause the page to expire?
I do not know if it makes difference, but I use Acegi, and regular login.jsp
page for login page,
not a Wicket managed page (I did not figure out how to use Wicket managed
login page with Acegi).
Lubos
igor.vaynb
hrm, i dont see how /MyApp/app can ever cause a page expired error because
it is a bookmarkable url and so a new instance of page is always created. i
would debug the request cycle and see why it cannot find the page, seems
very strange to me
-igor
On 7/28/07, lubosp <[EMAIL PROTECTED]> wrote:
>
Igor,
after login page (login.jsp) it is redirected to /MyApp/app which goes to my
wicket home page, and that one is expired.
Is it possible that I am missing something on logout action?
Is it enough to do session.invalidate()?
Note, it works properly the first time, only after I log out and t
what url causes the page expired page?
-igor
On 7/28/07, lubosp <[EMAIL PROTECTED]> wrote:
>
>
> Hi guys,
>
> my first wicket mailing list post. I just started using Wicket couple gays
> ago (after using Tapestry and ZK), and I have to say, I am impressed.
> Congratulation to great framework!
>
> Hi, I have some ajax link in a page that are used to select items in a
> list (the items are stored in an ArrayList on the server).
> It works fine with any browser. But from this page if I click on a
> BookmarkableLink to another page and after click on the back button
> of my browser, when cli
Hi Igor,
My bad, I had extended the pageexpiry page from my base page and it checks
for @Authorized. Though the page expired page came in the background it gets
navigated to login page. The issue is fixed now. I have changed it from
BasePage to WebPage. Your questions really helped me to debug th
also make sure your expired page doesnt throw an error, and check your logs
to make sure there arent any exceptions in there
-igor
On 2/3/07, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
its hard to help without seeing a working example. can you recreate in
quickstart?
-igor
On 2/3/07, sunraid
its hard to help without seeing a working example. can you recreate in
quickstart?
-igor
On 2/3/07, sunraider <[EMAIL PROTECTED]> wrote:
Hi Guys,
The page expired problem has resolved but now I am having a new problem
after I changed the stuff to pagemaps. When the session gets expired I
do
Hi Guys,
The page expired problem has resolved but now I am having a new problem
after I changed the stuff to pagemaps. When the session gets expired I dont
get the page expiry page.
I have the following set in My application.
getApplicationSettings().setPageExpiredErrorPage(PageExpiredErrorPag
Thank you guys, you are a great help!
Sajeev
igor.vaynberg wrote:
>
> there is also a frames example in wicket-examples
>
> -igor
>
>
> On 1/26/07, Marc-Andre Houle <[EMAIL PROTECTED]> wrote:
>>
>> Like Erik say, probably that using a different page map will help you
>> (Got
>> something li
there is also a frames example in wicket-examples
-igor
On 1/26/07, Marc-Andre Houle <[EMAIL PROTECTED]> wrote:
Like Erik say, probably that using a different page map will help you (Got
something like that when I didn't use the proper page map name someday.)
Give a look to the wiki under th
Like Erik say, probably that using a different page map will help you (Got
something like that when I didn't use the proper page map name someday.)
Give a look to the wiki under this page :
http://cwiki.apache.org/WICKET/using-frames.html
Marc
On 1/26/07, Erik van Oosten <[EMAIL PROTECTED]> wro
Hi Sajeev,
You should probably use another pagemap for each frame. This can be as
simple as adding the pageMapName attribute to the initial frame URL.
Regards,
Erik.
sunraider wrote:
> Hi,
>
> I am using Frames in my application, I have three framesets one with header
> second with tree (W
We'd need a bit more detail on your setup/ configuration etc. Does the
problem occor with all web browsers, or just a particular?
Wicket supports using the back button out-of-the-box, and page expiry
certainly points to something going wrong in your web app.
Eelco
On 7/12/06, [EMAIL PROTECTED]
Hmmm, I remember having such problems
before. The problem was with firefox generating invalid requests
because of a bad script in my page. Look at
(http://www.wicket-wiki.org.uk/wiki/index.php/Best_Practices_and_Gotchas)
to read about it. However, what we can do here is see what exactly is
caus
That happens because your session is invalidated on a restart. I think
tomcat serializes its sessions first, so on a restart of Tomcat you can
continue with the same/ reloaded session.
No way to avoid in as far as I know. B.t.w, all bookmarkable pages
should work without a problem, as they don't n
not if you where on a bookmarkable page
Or if jetty stores the session on disk and read them back in if you restart.
If both is not the case then the session isn't there any more and we
can't construct the components/page
so we have no idea where to dispatch the request. So the page was expired.
Hmmm. I have no idea... could you send me (some of your) code to my
personal email address?
Eelco
Matej Knopp wrote:
Hi.
I'm getting a page expired error and I don't know why. I'm using
wicket RC2. Every page expires on 10th reload. This only happens with
internet explorer. Mozilla and Opera ca
26 matches
Mail list logo
