Re: [Wicket-user] Page Expiration when first clicking AJAX
Hi Jonathan, developing against a recent trunk I made a strange obeservation which might be connected to this. I have a page with several wicketAjaxGet calls. Some of em work fine. The others behave strange, if clicked/called right after the page was loaded they are answered with a Page Expired. If called after some other fine working ones were called, those strange ones behaved just as expected. Loading the page wicket complained with a: ERROR org.apache.wicket.RequestCycle - the requested resource was not found org.apache.wicket.WicketRuntimeException: the requested resource was not found at org.apache.wicket.util.resource.WebExternalResourceStream.getInputStream(WebExternalResourceStream.java:99) The page was delivered to the client without any warnings on the client side. The missing resource was a 'style.css'. After I took care of that the Page worked fine, all wicketAjaxGet calls worked as expected. BTW, could someone please take care of: https://issues.apache.org/jira/browse/WICKET-582 Debugging the problem I noticed that Page Expired was given cause of line 114 in WebRequestCycleProcessor: // the page is no longer the active page // - ignore this request processRequest = false; Beyond this a breakpoint on AccessStackPageMap [line: 284] - put(Page) showed that on initial load of the page the page itself was put on the AccessStack and right after this an ExceptionErrorPage was put on that stack. The ExceptionErrorPage.id was the page.id incremented by one. And this is the point were I got lost. Maybe someone else has a better overview. Martin Jonathan Locke schrieb: Did we find a resolution for this yet? We are having the same problem in Wicket 1.3 trunk and I'm about to start investigating. Any definite information or conclusions (whether complete or not) would be very much appreciated. Andrew Berman wrote: I am having a strange issue. If I access my site for the first time (I clear all cookies, sessions, and cache before going to the site), the page comes up fine. However, if I click one of the AJAX links, I get a page expired error. Any thoughts why this is happening? I see it create a new session and the cookie, but it looks like the Ajax link is not valid for some reason. I am using Wicket 1.2.6. Any thoughts? Thanks for any help, Andrew - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] Page Expiration when first clicking AJAX
I commented out the DefaultServlet that comes with Tomcat and that seems to have resolved the issue (at least I can no longer replicate it on my local machine). I don't know why, but I'm guessing that since my app is mapped to / and tomcat's DefaultServlet is mapped to / it creates a session for the DefaultServlet and then for mine which explains why the session ids did not match. I'm going to test it in production and see if the problem is indeed resolved. On 5/19/07, Jonathan Locke [EMAIL PROTECTED] wrote: sorry, no. that was not wicket's javascript. Andrew Berman wrote: Interesting. I'm only using Wicket for my AJAX, so are you saying that something is wrong with the Wicket AJAX JavaScript? On 5/19/07, Jonathan Locke [EMAIL PROTECTED] wrote: i discovered in my case that this was related to cookie overflow created by some errant javascript on the page doing ajax callbacks. it had nothing to do with wicket. you might try modifying a build of wicket to diagnose your problem. i wound up putting some print statements in wicket where sessions are created to dump the jsessionid then finally putting alert statements in the javascript. Andrew Berman wrote: I haven't found a solution yet. I'm still debugging stuff and have no solution. The problem definitely occurs when the initial redirect occurs from /context to /context/YourHomePage. On 5/17/07, Jonathan Locke [EMAIL PROTECTED] wrote: Did we find a resolution for this yet? We are having the same problem in Wicket 1.3 trunk and I'm about to start investigating. Any definite information or conclusions (whether complete or not) would be very much appreciated. Andrew Berman wrote: I am having a strange issue. If I access my site for the first time (I clear all cookies, sessions, and cache before going to the site), the page comes up fine. However, if I click one of the AJAX links, I get a page expired error. Any thoughts why this is happening? I see it create a new session and the cookie, but it looks like the Ajax link is not valid for some reason. I am using Wicket 1.2.6. Any thoughts? Thanks for any help, Andrew - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user -- View this message in context: http://www.nabble.com/Page-Expiration-when-first-clicking-AJAX-tf3729176.html#a10669922 Sent from the Wicket - User mailing list archive at Nabble.com. - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user -- View this message in context: http://www.nabble.com/Page-Expiration-when-first-clicking-AJAX-tf3729176.html#a10700976 Sent from the Wicket - User mailing list archive at Nabble.com. - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user -- View this message in
Re: [Wicket-user] Page Expiration when first clicking AJAX
I haven't found a solution yet. I'm still debugging stuff and have no solution. The problem definitely occurs when the initial redirect occurs from /context to /context/YourHomePage. On 5/17/07, Jonathan Locke [EMAIL PROTECTED] wrote: Did we find a resolution for this yet? We are having the same problem in Wicket 1.3 trunk and I'm about to start investigating. Any definite information or conclusions (whether complete or not) would be very much appreciated. Andrew Berman wrote: I am having a strange issue. If I access my site for the first time (I clear all cookies, sessions, and cache before going to the site), the page comes up fine. However, if I click one of the AJAX links, I get a page expired error. Any thoughts why this is happening? I see it create a new session and the cookie, but it looks like the Ajax link is not valid for some reason. I am using Wicket 1.2.6. Any thoughts? Thanks for any help, Andrew - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user -- View this message in context: http://www.nabble.com/Page-Expiration-when-first-clicking-AJAX-tf3729176.html#a10669922 Sent from the Wicket - User mailing list archive at Nabble.com. - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] Page Expiration when first clicking AJAX
i discovered in my case that this was related to cookie overflow created by some errant javascript on the page doing ajax callbacks. it had nothing to do with wicket. you might try modifying a build of wicket to diagnose your problem. i wound up putting some print statements in wicket where sessions are created to dump the jsessionid then finally putting alert statements in the javascript. Andrew Berman wrote: I haven't found a solution yet. I'm still debugging stuff and have no solution. The problem definitely occurs when the initial redirect occurs from /context to /context/YourHomePage. On 5/17/07, Jonathan Locke [EMAIL PROTECTED] wrote: Did we find a resolution for this yet? We are having the same problem in Wicket 1.3 trunk and I'm about to start investigating. Any definite information or conclusions (whether complete or not) would be very much appreciated. Andrew Berman wrote: I am having a strange issue. If I access my site for the first time (I clear all cookies, sessions, and cache before going to the site), the page comes up fine. However, if I click one of the AJAX links, I get a page expired error. Any thoughts why this is happening? I see it create a new session and the cookie, but it looks like the Ajax link is not valid for some reason. I am using Wicket 1.2.6. Any thoughts? Thanks for any help, Andrew - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user -- View this message in context: http://www.nabble.com/Page-Expiration-when-first-clicking-AJAX-tf3729176.html#a10669922 Sent from the Wicket - User mailing list archive at Nabble.com. - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user -- View this message in context: http://www.nabble.com/Page-Expiration-when-first-clicking-AJAX-tf3729176.html#a10700976 Sent from the Wicket - User mailing list archive at Nabble.com. - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] Page Expiration when first clicking AJAX
Interesting. I'm only using Wicket for my AJAX, so are you saying that something is wrong with the Wicket AJAX JavaScript? On 5/19/07, Jonathan Locke [EMAIL PROTECTED] wrote: i discovered in my case that this was related to cookie overflow created by some errant javascript on the page doing ajax callbacks. it had nothing to do with wicket. you might try modifying a build of wicket to diagnose your problem. i wound up putting some print statements in wicket where sessions are created to dump the jsessionid then finally putting alert statements in the javascript. Andrew Berman wrote: I haven't found a solution yet. I'm still debugging stuff and have no solution. The problem definitely occurs when the initial redirect occurs from /context to /context/YourHomePage. On 5/17/07, Jonathan Locke [EMAIL PROTECTED] wrote: Did we find a resolution for this yet? We are having the same problem in Wicket 1.3 trunk and I'm about to start investigating. Any definite information or conclusions (whether complete or not) would be very much appreciated. Andrew Berman wrote: I am having a strange issue. If I access my site for the first time (I clear all cookies, sessions, and cache before going to the site), the page comes up fine. However, if I click one of the AJAX links, I get a page expired error. Any thoughts why this is happening? I see it create a new session and the cookie, but it looks like the Ajax link is not valid for some reason. I am using Wicket 1.2.6. Any thoughts? Thanks for any help, Andrew - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user -- View this message in context: http://www.nabble.com/Page-Expiration-when-first-clicking-AJAX-tf3729176.html#a10669922 Sent from the Wicket - User mailing list archive at Nabble.com. - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user -- View this message in context: http://www.nabble.com/Page-Expiration-when-first-clicking-AJAX-tf3729176.html#a10700976 Sent from the Wicket - User mailing list archive at Nabble.com. - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] Page Expiration when first clicking AJAX
sorry, no. that was not wicket's javascript. Andrew Berman wrote: Interesting. I'm only using Wicket for my AJAX, so are you saying that something is wrong with the Wicket AJAX JavaScript? On 5/19/07, Jonathan Locke [EMAIL PROTECTED] wrote: i discovered in my case that this was related to cookie overflow created by some errant javascript on the page doing ajax callbacks. it had nothing to do with wicket. you might try modifying a build of wicket to diagnose your problem. i wound up putting some print statements in wicket where sessions are created to dump the jsessionid then finally putting alert statements in the javascript. Andrew Berman wrote: I haven't found a solution yet. I'm still debugging stuff and have no solution. The problem definitely occurs when the initial redirect occurs from /context to /context/YourHomePage. On 5/17/07, Jonathan Locke [EMAIL PROTECTED] wrote: Did we find a resolution for this yet? We are having the same problem in Wicket 1.3 trunk and I'm about to start investigating. Any definite information or conclusions (whether complete or not) would be very much appreciated. Andrew Berman wrote: I am having a strange issue. If I access my site for the first time (I clear all cookies, sessions, and cache before going to the site), the page comes up fine. However, if I click one of the AJAX links, I get a page expired error. Any thoughts why this is happening? I see it create a new session and the cookie, but it looks like the Ajax link is not valid for some reason. I am using Wicket 1.2.6. Any thoughts? Thanks for any help, Andrew - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user -- View this message in context: http://www.nabble.com/Page-Expiration-when-first-clicking-AJAX-tf3729176.html#a10669922 Sent from the Wicket - User mailing list archive at Nabble.com. - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user -- View this message in context: http://www.nabble.com/Page-Expiration-when-first-clicking-AJAX-tf3729176.html#a10700976 Sent from the Wicket - User mailing list archive at Nabble.com. - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user -- View this message in context: http://www.nabble.com/Page-Expiration-when-first-clicking-AJAX-tf3729176.html#a10701576 Sent from the Wicket - User mailing list archive at Nabble.com. - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Wicket-user
Re: [Wicket-user] Page Expiration when first clicking AJAX
Did we find a resolution for this yet? We are having the same problem in Wicket 1.3 trunk and I'm about to start investigating. Any definite information or conclusions (whether complete or not) would be very much appreciated. Andrew Berman wrote: I am having a strange issue. If I access my site for the first time (I clear all cookies, sessions, and cache before going to the site), the page comes up fine. However, if I click one of the AJAX links, I get a page expired error. Any thoughts why this is happening? I see it create a new session and the cookie, but it looks like the Ajax link is not valid for some reason. I am using Wicket 1.2.6. Any thoughts? Thanks for any help, Andrew - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user -- View this message in context: http://www.nabble.com/Page-Expiration-when-first-clicking-AJAX-tf3729176.html#a10669922 Sent from the Wicket - User mailing list archive at Nabble.com. - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] Page Expiration when first clicking AJAX
HomePage is the actual page itself. The mount is just what I mounted in the Application class using: mount(/app, PackageName.forClass(getHomePage())); On 5/15/07, Igor Vaynberg [EMAIL PROTECTED] wrote: if your homepage is mounted to /app then the url should be /context/app. so where does HomePage come from? -igor On 5/15/07, Andrew Berman [EMAIL PROTECTED] wrote: It's mapped to /context/* and the HomePage class is mounted to /app, so the url for the homepage is http://blah.com/context/app/HomePage. Going directly to http://blah.com/context redirects to http://blah.com/context/app/HomePage On 5/15/07, Igor Vaynberg [EMAIL PROTECTED] wrote: so wicket is mapped to /* but homepage is mounted to /app/homepage? -igor On 5/15/07, Andrew Berman [EMAIL PROTECTED] wrote: I'm not doing any redirect using index.html and a meta redirect. I just call blah.com/context and Wicket is doing the redirect to /app/homepage. /app is what I use for the mount point. On 5/15/07, Igor Vaynberg [EMAIL PROTECTED] wrote: i dont think that is it. jsessionid is only appended when there is a session. when you hit blah.com/context you are probably hitting index.htmlthat does a metaredirect to blah.com/context/app/homepage. so on the first hit to blah.com/context there is no session. now when you hit /app/home a session is created, and cookie is set. -igor On 5/15/07, Andrew Berman [EMAIL PROTECTED] wrote: I'm going to debug it a bit more to see what's going on. The jsessionid is not appended to the URL until Wicket performs a redirect from the context to the actual home page (e.g. from http://blah.com/context redirects to http://blah.com/context/app/HomePage), so I'm wondering if the redirect is doing something that's causing Tomcat to think it's a new session, thereby making the jsessionid in the URL not equal the one in the cookie. Eelco, I'll take a look at what you're saying too and see if I can reconfigure Tomcat as well. On 5/15/07, Eelco Hillenius [EMAIL PROTECTED] wrote: Also, sessions are managed by the app server, not by Wicket or Spring MVC. I had a problem a while ago losing sessions going from foo.mydomain.com to bar.mydomain.com, and that only worked well when I configured Jetty's session manager to use .mydomain.com as it's session domain. Maybe your problem is similar? Or even if it isn't, what I'm saying is that it is very unlikely Wicket or any other framework is the bad guy as Wicket just uses the servlet API as-is. Eelco On 5/15/07, Johan Compagner [EMAIL PROTECTED] wrote: can you look at the first request if the wicket session is really pushed to the http session (so is the http session created?) you can look at that in the set atribute of the session store On 5/15/07, Andrew Berman [EMAIL PROTECTED] wrote: I think I found the crux of the problem. When you first go to the app, as I've mentioned, it puts the jsessionid in the URL. Well, I compared that sessionid to the one in the cookie created and they are different! That has to be the reason it creates a new session. Now to figure out why it's doing that. On 5/14/07, Andrew Berman [EMAIL PROTECTED] wrote: Spring MVC does put the jsessionid in the URL. What I don't understand is that when coming into the Wicket app for the first time, it goes to the home page fine with the jsessionid in the URL, and then I click any link and all session attributes are gone. Literally a brand new session is created no matter what link I click. However, once I click that next link, all is fine and that second new session is the one that is used. Just doesn't make any sense. On 5/14/07, Eelco Hillenius [EMAIL PROTECTED] wrote: Definitely not what I want, but it's the only thing that works. There's clearly a problem in how Wicket is getting the session from the cookie. My Spring MVC app which uses the same WAR has no issues pulling the session info. I don't really understand the problem though. Like Johan said, the first time a persistent session is made, Tomcat puts the session id in the URL as it doesn't know yet whether it can rely on cookies (if I understand correctly). Spring MVC might not do that for the particular things you test it for as it doesn't create a session? If you would use stateless
Re: [Wicket-user] Page Expiration when first clicking AJAX
So I've been debugging this pretty extensively now. I put a breakpoint in WicketServlet. 1. On the first request (http://blah.com/context), the session id in the URL and in the session all match and when I look at the cookie the jsessionid also matches. 2. On the last request, the session id is the same as in the first request. 3. When all requests are finished, the URL displays the original session id, BUT the cookie is showing some new session id. So somehow, the original cookie is being overwritten with a new cookie which includes a new jsessionid. Anyone have any thoughts on this? A new cookie should not be created when a redirect occurs, right? If the URL could change to the new session id this would also solve the problem. On 5/16/07, Andrew Berman [EMAIL PROTECTED] wrote: HomePage is the actual page itself. The mount is just what I mounted in the Application class using: mount(/app, PackageName.forClass (getHomePage())); On 5/15/07, Igor Vaynberg [EMAIL PROTECTED] wrote: if your homepage is mounted to /app then the url should be /context/app. so where does HomePage come from? -igor On 5/15/07, Andrew Berman [EMAIL PROTECTED] wrote: It's mapped to /context/* and the HomePage class is mounted to /app, so the url for the homepage is http://blah.com/context/app/HomePage. Going directly to http://blah.com/context redirects to http://blah.com/context/app/HomePage On 5/15/07, Igor Vaynberg [EMAIL PROTECTED] wrote: so wicket is mapped to /* but homepage is mounted to /app/homepage? -igor On 5/15/07, Andrew Berman [EMAIL PROTECTED] wrote: I'm not doing any redirect using index.html and a meta redirect. I just call blah.com/context and Wicket is doing the redirect to /app/homepage. /app is what I use for the mount point. On 5/15/07, Igor Vaynberg [EMAIL PROTECTED] wrote: i dont think that is it. jsessionid is only appended when there is a session. when you hit blah.com/context you are probably hitting index.html that does a metaredirect to blah.com/context/app/homepage. so on the first hit to blah.com/context there is no session. now when you hit /app/home a session is created, and cookie is set. -igor On 5/15/07, Andrew Berman [EMAIL PROTECTED] wrote: I'm going to debug it a bit more to see what's going on. The jsessionid is not appended to the URL until Wicket performs a redirect from the context to the actual home page (e.g. from http://blah.com/context redirects to http://blah.com/context/app/HomePage), so I'm wondering if the redirect is doing something that's causing Tomcat to think it's a new session, thereby making the jsessionid in the URL not equal the one in the cookie. Eelco, I'll take a look at what you're saying too and see if I can reconfigure Tomcat as well. On 5/15/07, Eelco Hillenius [EMAIL PROTECTED] wrote: Also, sessions are managed by the app server, not by Wicket or Spring MVC. I had a problem a while ago losing sessions going from foo.mydomain.com to bar.mydomain.com, and that only worked well when I configured Jetty's session manager to use .mydomain.com as it's session domain. Maybe your problem is similar? Or even if it isn't, what I'm saying is that it is very unlikely Wicket or any other framework is the bad guy as Wicket just uses the servlet API as-is. Eelco On 5/15/07, Johan Compagner [EMAIL PROTECTED] wrote: can you look at the first request if the wicket session is really pushed to the http session (so is the http session created?) you can look at that in the set atribute of the session store On 5/15/07, Andrew Berman [EMAIL PROTECTED] wrote: I think I found the crux of the problem. When you first go to the app, as I've mentioned, it puts the jsessionid in the URL. Well, I compared that sessionid to the one in the cookie created and they are different! That has to be the reason it creates a new session. Now to figure out why it's doing that. On 5/14/07, Andrew Berman [EMAIL PROTECTED] wrote: Spring MVC does put the jsessionid in the URL. What I don't understand is that when coming into the Wicket app for the first time, it goes to the home page fine with the jsessionid in the URL, and then I click any link and all session attributes are gone. Literally a brand new session is created no matter what link I click. However, once I click that next link, all is fine and that second new session is the one that is
Re: [Wicket-user] Page Expiration when first clicking AJAX
can you look at the first request if the wicket session is really pushed to the http session (so is the http session created?) you can look at that in the set atribute of the session store On 5/15/07, Andrew Berman [EMAIL PROTECTED] wrote: I think I found the crux of the problem. When you first go to the app, as I've mentioned, it puts the jsessionid in the URL. Well, I compared that sessionid to the one in the cookie created and they are different! That has to be the reason it creates a new session. Now to figure out why it's doing that. On 5/14/07, Andrew Berman [EMAIL PROTECTED] wrote: Spring MVC does put the jsessionid in the URL. What I don't understand is that when coming into the Wicket app for the first time, it goes to the home page fine with the jsessionid in the URL, and then I click any link and all session attributes are gone. Literally a brand new session is created no matter what link I click. However, once I click that next link, all is fine and that second new session is the one that is used. Just doesn't make any sense. On 5/14/07, Eelco Hillenius [EMAIL PROTECTED] wrote: Definitely not what I want, but it's the only thing that works. There's clearly a problem in how Wicket is getting the session from the cookie. My Spring MVC app which uses the same WAR has no issues pulling the session info. I don't really understand the problem though. Like Johan said, the first time a persistent session is made, Tomcat puts the session id in the URL as it doesn't know yet whether it can rely on cookies (if I understand correctly). Spring MVC might not do that for the particular things you test it for as it doesn't create a session? If you would use stateless pages Wicket wouldn't either. Anyway, there have been discussions about jsessionid on the lists before, and typically it was from people worrying it would mess up search bots etc. If you are worried about that, don't, as bots can filter it. Also, the url is stable as it is not part of the parameters part (which comes after the question mark). It's a universal Java app server thingy, and Wicket has nothing to do with it other than it probably relies on the HttpSession sooner than e.g. model 2 frameworks. Eelco - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] Page Expiration when first clicking AJAX
Also, sessions are managed by the app server, not by Wicket or Spring MVC. I had a problem a while ago losing sessions going from foo.mydomain.com to bar.mydomain.com, and that only worked well when I configured Jetty's session manager to use .mydomain.com as it's session domain. Maybe your problem is similar? Or even if it isn't, what I'm saying is that it is very unlikely Wicket or any other framework is the bad guy as Wicket just uses the servlet API as-is. Eelco On 5/15/07, Johan Compagner [EMAIL PROTECTED] wrote: can you look at the first request if the wicket session is really pushed to the http session (so is the http session created?) you can look at that in the set atribute of the session store On 5/15/07, Andrew Berman [EMAIL PROTECTED] wrote: I think I found the crux of the problem. When you first go to the app, as I've mentioned, it puts the jsessionid in the URL. Well, I compared that sessionid to the one in the cookie created and they are different! That has to be the reason it creates a new session. Now to figure out why it's doing that. On 5/14/07, Andrew Berman [EMAIL PROTECTED] wrote: Spring MVC does put the jsessionid in the URL. What I don't understand is that when coming into the Wicket app for the first time, it goes to the home page fine with the jsessionid in the URL, and then I click any link and all session attributes are gone. Literally a brand new session is created no matter what link I click. However, once I click that next link, all is fine and that second new session is the one that is used. Just doesn't make any sense. On 5/14/07, Eelco Hillenius [EMAIL PROTECTED] wrote: Definitely not what I want, but it's the only thing that works. There's clearly a problem in how Wicket is getting the session from the cookie. My Spring MVC app which uses the same WAR has no issues pulling the session info. I don't really understand the problem though. Like Johan said, the first time a persistent session is made, Tomcat puts the session id in the URL as it doesn't know yet whether it can rely on cookies (if I understand correctly). Spring MVC might not do that for the particular things you test it for as it doesn't create a session? If you would use stateless pages Wicket wouldn't either. Anyway, there have been discussions about jsessionid on the lists before, and typically it was from people worrying it would mess up search bots etc. If you are worried about that, don't, as bots can filter it. Also, the url is stable as it is not part of the parameters part (which comes after the question mark). It's a universal Java app server thingy, and Wicket has nothing to do with it other than it probably relies on the HttpSession sooner than e.g. model 2 frameworks. Eelco - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] Page Expiration when first clicking AJAX
I'm going to debug it a bit more to see what's going on. The jsessionid is not appended to the URL until Wicket performs a redirect from the context to the actual home page (e.g. from http://blah.com/context redirects to http://blah.com/context/app/HomePage), so I'm wondering if the redirect is doing something that's causing Tomcat to think it's a new session, thereby making the jsessionid in the URL not equal the one in the cookie. Eelco, I'll take a look at what you're saying too and see if I can reconfigure Tomcat as well. On 5/15/07, Eelco Hillenius [EMAIL PROTECTED] wrote: Also, sessions are managed by the app server, not by Wicket or Spring MVC. I had a problem a while ago losing sessions going from foo.mydomain.com to bar.mydomain.com, and that only worked well when I configured Jetty's session manager to use .mydomain.com as it's session domain. Maybe your problem is similar? Or even if it isn't, what I'm saying is that it is very unlikely Wicket or any other framework is the bad guy as Wicket just uses the servlet API as-is. Eelco On 5/15/07, Johan Compagner [EMAIL PROTECTED] wrote: can you look at the first request if the wicket session is really pushed to the http session (so is the http session created?) you can look at that in the set atribute of the session store On 5/15/07, Andrew Berman [EMAIL PROTECTED] wrote: I think I found the crux of the problem. When you first go to the app, as I've mentioned, it puts the jsessionid in the URL. Well, I compared that sessionid to the one in the cookie created and they are different! That has to be the reason it creates a new session. Now to figure out why it's doing that. On 5/14/07, Andrew Berman [EMAIL PROTECTED] wrote: Spring MVC does put the jsessionid in the URL. What I don't understand is that when coming into the Wicket app for the first time, it goes to the home page fine with the jsessionid in the URL, and then I click any link and all session attributes are gone. Literally a brand new session is created no matter what link I click. However, once I click that next link, all is fine and that second new session is the one that is used. Just doesn't make any sense. On 5/14/07, Eelco Hillenius [EMAIL PROTECTED] wrote: Definitely not what I want, but it's the only thing that works. There's clearly a problem in how Wicket is getting the session from the cookie. My Spring MVC app which uses the same WAR has no issues pulling the session info. I don't really understand the problem though. Like Johan said, the first time a persistent session is made, Tomcat puts the session id in the URL as it doesn't know yet whether it can rely on cookies (if I understand correctly). Spring MVC might not do that for the particular things you test it for as it doesn't create a session? If you would use stateless pages Wicket wouldn't either. Anyway, there have been discussions about jsessionid on the lists before, and typically it was from people worrying it would mess up search bots etc. If you are worried about that, don't, as bots can filter it. Also, the url is stable as it is not part of the parameters part (which comes after the question mark). It's a universal Java app server thingy, and Wicket has nothing to do with it other than it probably relies on the HttpSession sooner than e.g. model 2 frameworks. Eelco - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user -
Re: [Wicket-user] Page Expiration when first clicking AJAX
i dont think that is it. jsessionid is only appended when there is a session. when you hit blah.com/context you are probably hitting index.html that does a metaredirect to blah.com/context/app/homepage. so on the first hit to blah.com/context there is no session. now when you hit /app/home a session is created, and cookie is set. -igor On 5/15/07, Andrew Berman [EMAIL PROTECTED] wrote: I'm going to debug it a bit more to see what's going on. The jsessionid is not appended to the URL until Wicket performs a redirect from the context to the actual home page (e.g. from http://blah.com/context redirects to http://blah.com/context/app/HomePage), so I'm wondering if the redirect is doing something that's causing Tomcat to think it's a new session, thereby making the jsessionid in the URL not equal the one in the cookie. Eelco, I'll take a look at what you're saying too and see if I can reconfigure Tomcat as well. On 5/15/07, Eelco Hillenius [EMAIL PROTECTED] wrote: Also, sessions are managed by the app server, not by Wicket or Spring MVC. I had a problem a while ago losing sessions going from foo.mydomain.com to bar.mydomain.com, and that only worked well when I configured Jetty's session manager to use .mydomain.com as it's session domain. Maybe your problem is similar? Or even if it isn't, what I'm saying is that it is very unlikely Wicket or any other framework is the bad guy as Wicket just uses the servlet API as-is. Eelco On 5/15/07, Johan Compagner [EMAIL PROTECTED] wrote: can you look at the first request if the wicket session is really pushed to the http session (so is the http session created?) you can look at that in the set atribute of the session store On 5/15/07, Andrew Berman [EMAIL PROTECTED] wrote: I think I found the crux of the problem. When you first go to the app, as I've mentioned, it puts the jsessionid in the URL. Well, I compared that sessionid to the one in the cookie created and they are different! That has to be the reason it creates a new session. Now to figure out why it's doing that. On 5/14/07, Andrew Berman [EMAIL PROTECTED] wrote: Spring MVC does put the jsessionid in the URL. What I don't understand is that when coming into the Wicket app for the first time, it goes to the home page fine with the jsessionid in the URL, and then I click any link and all session attributes are gone. Literally a brand new session is created no matter what link I click. However, once I click that next link, all is fine and that second new session is the one that is used. Just doesn't make any sense. On 5/14/07, Eelco Hillenius [EMAIL PROTECTED] wrote: Definitely not what I want, but it's the only thing that works. There's clearly a problem in how Wicket is getting the session from the cookie. My Spring MVC app which uses the same WAR has no issues pulling the session info. I don't really understand the problem though. Like Johan said, the first time a persistent session is made, Tomcat puts the session id in the URL as it doesn't know yet whether it can rely on cookies (if I understand correctly). Spring MVC might not do that for the particular things you test it for as it doesn't create a session? If you would use stateless pages Wicket wouldn't either. Anyway, there have been discussions about jsessionid on the lists before, and typically it was from people worrying it would mess up search bots etc. If you are worried about that, don't, as bots can filter it. Also, the url is stable as it is not part of the parameters part (which comes after the question mark). It's a universal Java app server thingy, and Wicket has nothing to do with it other than it probably relies on the HttpSession sooner than e.g. model 2 frameworks. Eelco - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] Page Expiration when first clicking AJAX
I'm not doing any redirect using index.html and a meta redirect. I just call blah.com/context and Wicket is doing the redirect to /app/homepage. /app is what I use for the mount point. On 5/15/07, Igor Vaynberg [EMAIL PROTECTED] wrote: i dont think that is it. jsessionid is only appended when there is a session. when you hit blah.com/context you are probably hitting index.html that does a metaredirect to blah.com/context/app/homepage. so on the first hit to blah.com/context there is no session. now when you hit /app/home a session is created, and cookie is set. -igor On 5/15/07, Andrew Berman [EMAIL PROTECTED] wrote: I'm going to debug it a bit more to see what's going on. The jsessionid is not appended to the URL until Wicket performs a redirect from the context to the actual home page (e.g. from http://blah.com/context redirects to http://blah.com/context/app/HomePage), so I'm wondering if the redirect is doing something that's causing Tomcat to think it's a new session, thereby making the jsessionid in the URL not equal the one in the cookie. Eelco, I'll take a look at what you're saying too and see if I can reconfigure Tomcat as well. On 5/15/07, Eelco Hillenius [EMAIL PROTECTED] wrote: Also, sessions are managed by the app server, not by Wicket or Spring MVC. I had a problem a while ago losing sessions going from foo.mydomain.com to bar.mydomain.com, and that only worked well when I configured Jetty's session manager to use .mydomain.com as it's session domain. Maybe your problem is similar? Or even if it isn't, what I'm saying is that it is very unlikely Wicket or any other framework is the bad guy as Wicket just uses the servlet API as-is. Eelco On 5/15/07, Johan Compagner [EMAIL PROTECTED] wrote: can you look at the first request if the wicket session is really pushed to the http session (so is the http session created?) you can look at that in the set atribute of the session store On 5/15/07, Andrew Berman [EMAIL PROTECTED] wrote: I think I found the crux of the problem. When you first go to the app, as I've mentioned, it puts the jsessionid in the URL. Well, I compared that sessionid to the one in the cookie created and they are different! That has to be the reason it creates a new session. Now to figure out why it's doing that. On 5/14/07, Andrew Berman [EMAIL PROTECTED] wrote: Spring MVC does put the jsessionid in the URL. What I don't understand is that when coming into the Wicket app for the first time, it goes to the home page fine with the jsessionid in the URL, and then I click any link and all session attributes are gone. Literally a brand new session is created no matter what link I click. However, once I click that next link, all is fine and that second new session is the one that is used. Just doesn't make any sense. On 5/14/07, Eelco Hillenius [EMAIL PROTECTED] wrote: Definitely not what I want, but it's the only thing that works. There's clearly a problem in how Wicket is getting the session from the cookie. My Spring MVC app which uses the same WAR has no issues pulling the session info. I don't really understand the problem though. Like Johan said, the first time a persistent session is made, Tomcat puts the session id in the URL as it doesn't know yet whether it can rely on cookies (if I understand correctly). Spring MVC might not do that for the particular things you test it for as it doesn't create a session? If you would use stateless pages Wicket wouldn't either. Anyway, there have been discussions about jsessionid on the lists before, and typically it was from people worrying it would mess up search bots etc. If you are worried about that, don't, as bots can filter it. Also, the url is stable as it is not part of the parameters part (which comes after the question mark). It's a universal Java app server thingy, and Wicket has nothing to do with it other than it probably relies on the HttpSession sooner than e.g. model 2 frameworks. Eelco - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - This SF.net email is sponsored by DB2 Express
Re: [Wicket-user] Page Expiration when first clicking AJAX
so wicket is mapped to /* but homepage is mounted to /app/homepage? -igor On 5/15/07, Andrew Berman [EMAIL PROTECTED] wrote: I'm not doing any redirect using index.html and a meta redirect. I just call blah.com/context and Wicket is doing the redirect to /app/homepage. /app is what I use for the mount point. On 5/15/07, Igor Vaynberg [EMAIL PROTECTED] wrote: i dont think that is it. jsessionid is only appended when there is a session. when you hit blah.com/context you are probably hitting index.html that does a metaredirect to blah.com/context/app/homepage. so on the first hit to blah.com/context there is no session. now when you hit /app/home a session is created, and cookie is set. -igor On 5/15/07, Andrew Berman [EMAIL PROTECTED] wrote: I'm going to debug it a bit more to see what's going on. The jsessionid is not appended to the URL until Wicket performs a redirect from the context to the actual home page (e.g. from http://blah.com/contextredirects to http://blah.com/context/app/HomePage), so I'm wondering if the redirect is doing something that's causing Tomcat to think it's a new session, thereby making the jsessionid in the URL not equal the one in the cookie. Eelco, I'll take a look at what you're saying too and see if I can reconfigure Tomcat as well. On 5/15/07, Eelco Hillenius [EMAIL PROTECTED] wrote: Also, sessions are managed by the app server, not by Wicket or Spring MVC. I had a problem a while ago losing sessions going from foo.mydomain.com to bar.mydomain.com, and that only worked well when I configured Jetty's session manager to use .mydomain.com as it's session domain. Maybe your problem is similar? Or even if it isn't, what I'm saying is that it is very unlikely Wicket or any other framework is the bad guy as Wicket just uses the servlet API as-is. Eelco On 5/15/07, Johan Compagner [EMAIL PROTECTED] wrote: can you look at the first request if the wicket session is really pushed to the http session (so is the http session created?) you can look at that in the set atribute of the session store On 5/15/07, Andrew Berman [EMAIL PROTECTED] wrote: I think I found the crux of the problem. When you first go to the app, as I've mentioned, it puts the jsessionid in the URL. Well, I compared that sessionid to the one in the cookie created and they are different! That has to be the reason it creates a new session. Now to figure out why it's doing that. On 5/14/07, Andrew Berman [EMAIL PROTECTED] wrote: Spring MVC does put the jsessionid in the URL. What I don't understand is that when coming into the Wicket app for the first time, it goes to the home page fine with the jsessionid in the URL, and then I click any link and all session attributes are gone. Literally a brand new session is created no matter what link I click. However, once I click that next link, all is fine and that second new session is the one that is used. Just doesn't make any sense. On 5/14/07, Eelco Hillenius [EMAIL PROTECTED] wrote: Definitely not what I want, but it's the only thing that works. There's clearly a problem in how Wicket is getting the session from the cookie. My Spring MVC app which uses the same WAR has no issues pulling the session info. I don't really understand the problem though. Like Johan said, the first time a persistent session is made, Tomcat puts the session id in the URL as it doesn't know yet whether it can rely on cookies (if I understand correctly). Spring MVC might not do that for the particular things you test it for as it doesn't create a session? If you would use stateless pages Wicket wouldn't either. Anyway, there have been discussions about jsessionid on the lists before, and typically it was from people worrying it would mess up search bots etc. If you are worried about that, don't, as bots can filter it. Also, the url is stable as it is not part of the parameters part (which comes after the question mark). It's a universal Java app server thingy, and Wicket has nothing to do with it other than it probably relies on the HttpSession sooner than e.g. model 2 frameworks. Eelco - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Wicket-user
Re: [Wicket-user] Page Expiration when first clicking AJAX
It's mapped to /context/* and the HomePage class is mounted to /app, so the url for the homepage is http://blah.com/context/app/HomePage. Going directly to http://blah.com/context redirects to http://blah.com/context/app/HomePage On 5/15/07, Igor Vaynberg [EMAIL PROTECTED] wrote: so wicket is mapped to /* but homepage is mounted to /app/homepage? -igor On 5/15/07, Andrew Berman [EMAIL PROTECTED] wrote: I'm not doing any redirect using index.html and a meta redirect. I just call blah.com/context and Wicket is doing the redirect to /app/homepage. /app is what I use for the mount point. On 5/15/07, Igor Vaynberg [EMAIL PROTECTED] wrote: i dont think that is it. jsessionid is only appended when there is a session. when you hit blah.com/context you are probably hitting index.html that does a metaredirect to blah.com/context/app/homepage. so on the first hit to blah.com/context there is no session. now when you hit /app/home a session is created, and cookie is set. -igor On 5/15/07, Andrew Berman [EMAIL PROTECTED] wrote: I'm going to debug it a bit more to see what's going on. The jsessionid is not appended to the URL until Wicket performs a redirect from the context to the actual home page (e.g. from http://blah.com/context redirects to http://blah.com/context/app/HomePage), so I'm wondering if the redirect is doing something that's causing Tomcat to think it's a new session, thereby making the jsessionid in the URL not equal the one in the cookie. Eelco, I'll take a look at what you're saying too and see if I can reconfigure Tomcat as well. On 5/15/07, Eelco Hillenius [EMAIL PROTECTED] wrote: Also, sessions are managed by the app server, not by Wicket or Spring MVC. I had a problem a while ago losing sessions going from foo.mydomain.com to bar.mydomain.com, and that only worked well when I configured Jetty's session manager to use .mydomain.com as it's session domain. Maybe your problem is similar? Or even if it isn't, what I'm saying is that it is very unlikely Wicket or any other framework is the bad guy as Wicket just uses the servlet API as-is. Eelco On 5/15/07, Johan Compagner [EMAIL PROTECTED] wrote: can you look at the first request if the wicket session is really pushed to the http session (so is the http session created?) you can look at that in the set atribute of the session store On 5/15/07, Andrew Berman [EMAIL PROTECTED] wrote: I think I found the crux of the problem. When you first go to the app, as I've mentioned, it puts the jsessionid in the URL. Well, I compared that sessionid to the one in the cookie created and they are different! That has to be the reason it creates a new session. Now to figure out why it's doing that. On 5/14/07, Andrew Berman [EMAIL PROTECTED] wrote: Spring MVC does put the jsessionid in the URL. What I don't understand is that when coming into the Wicket app for the first time, it goes to the home page fine with the jsessionid in the URL, and then I click any link and all session attributes are gone. Literally a brand new session is created no matter what link I click. However, once I click that next link, all is fine and that second new session is the one that is used. Just doesn't make any sense. On 5/14/07, Eelco Hillenius [EMAIL PROTECTED] wrote: Definitely not what I want, but it's the only thing that works. There's clearly a problem in how Wicket is getting the session from the cookie. My Spring MVC app which uses the same WAR has no issues pulling the session info. I don't really understand the problem though. Like Johan said, the first time a persistent session is made, Tomcat puts the session id in the URL as it doesn't know yet whether it can rely on cookies (if I understand correctly). Spring MVC might not do that for the particular things you test it for as it doesn't create a session? If you would use stateless pages Wicket wouldn't either. Anyway, there have been discussions about jsessionid on the lists before, and typically it was from people worrying it would mess up search bots etc. If you are worried about that, don't, as bots can filter it. Also, the url is stable as it is not part of the parameters part (which comes after the question mark). It's a universal Java app server thingy, and Wicket has nothing to do with it other than it probably relies on the HttpSession sooner than e.g. model 2 frameworks.
Re: [Wicket-user] Page Expiration when first clicking AJAX
if your homepage is mounted to /app then the url should be /context/app. so where does HomePage come from? -igor On 5/15/07, Andrew Berman [EMAIL PROTECTED] wrote: It's mapped to /context/* and the HomePage class is mounted to /app, so the url for the homepage is http://blah.com/context/app/HomePage. Going directly to http://blah.com/context redirects to http://blah.com/context/app/HomePage On 5/15/07, Igor Vaynberg [EMAIL PROTECTED] wrote: so wicket is mapped to /* but homepage is mounted to /app/homepage? -igor On 5/15/07, Andrew Berman [EMAIL PROTECTED] wrote: I'm not doing any redirect using index.html and a meta redirect. I just call blah.com/context and Wicket is doing the redirect to /app/homepage. /app is what I use for the mount point. On 5/15/07, Igor Vaynberg [EMAIL PROTECTED] wrote: i dont think that is it. jsessionid is only appended when there is a session. when you hit blah.com/context you are probably hitting index.htmlthat does a metaredirect to blah.com/context/app/homepage. so on the first hit to blah.com/context there is no session. now when you hit /app/home a session is created, and cookie is set. -igor On 5/15/07, Andrew Berman [EMAIL PROTECTED] wrote: I'm going to debug it a bit more to see what's going on. The jsessionid is not appended to the URL until Wicket performs a redirect from the context to the actual home page (e.g. from http://blah.com/context redirects to http://blah.com/context/app/HomePage), so I'm wondering if the redirect is doing something that's causing Tomcat to think it's a new session, thereby making the jsessionid in the URL not equal the one in the cookie. Eelco, I'll take a look at what you're saying too and see if I can reconfigure Tomcat as well. On 5/15/07, Eelco Hillenius [EMAIL PROTECTED] wrote: Also, sessions are managed by the app server, not by Wicket or Spring MVC. I had a problem a while ago losing sessions going from foo.mydomain.com to bar.mydomain.com, and that only worked well when I configured Jetty's session manager to use .mydomain.com as it's session domain. Maybe your problem is similar? Or even if it isn't, what I'm saying is that it is very unlikely Wicket or any other framework is the bad guy as Wicket just uses the servlet API as-is. Eelco On 5/15/07, Johan Compagner [EMAIL PROTECTED] wrote: can you look at the first request if the wicket session is really pushed to the http session (so is the http session created?) you can look at that in the set atribute of the session store On 5/15/07, Andrew Berman [EMAIL PROTECTED] wrote: I think I found the crux of the problem. When you first go to the app, as I've mentioned, it puts the jsessionid in the URL. Well, I compared that sessionid to the one in the cookie created and they are different! That has to be the reason it creates a new session. Now to figure out why it's doing that. On 5/14/07, Andrew Berman [EMAIL PROTECTED] wrote: Spring MVC does put the jsessionid in the URL. What I don't understand is that when coming into the Wicket app for the first time, it goes to the home page fine with the jsessionid in the URL, and then I click any link and all session attributes are gone. Literally a brand new session is created no matter what link I click. However, once I click that next link, all is fine and that second new session is the one that is used. Just doesn't make any sense. On 5/14/07, Eelco Hillenius [EMAIL PROTECTED] wrote: Definitely not what I want, but it's the only thing that works. There's clearly a problem in how Wicket is getting the session from the cookie. My Spring MVC app which uses the same WAR has no issues pulling the session info. I don't really understand the problem though. Like Johan said, the first time a persistent session is made, Tomcat puts the session id in the URL as it doesn't know yet whether it can rely on cookies (if I understand correctly). Spring MVC might not do that for the particular things you test it for as it doesn't create a session? If you would use stateless pages Wicket wouldn't either. Anyway, there have been discussions about jsessionid on the lists before, and typically it was from people worrying it would mess up search bots etc. If you are worried about that, don't, as bots can filter it. Also, the url is stable as it is not part
Re: [Wicket-user] Page Expiration when first clicking AJAX
I'm willing to try anything to try to workaround or fix this problem. Does anyone have any suggestions where I should start looking or playing around in the Wicket code to figure out possibly what is going on? On 5/13/07, Jonathan Locke [EMAIL PROTECTED] wrote: we're getting some issue like this too and on only one server. Eelco Hillenius wrote: Are you working on multiple servers? On 5/12/07, Andrew Berman [EMAIL PROTECTED] wrote: Igor, Eelco, anyone? This issue is pretty major as I'm losing all the session info when they first come into the app On 5/11/07, Andrew Berman [EMAIL PROTECTED] wrote: Could there be an issue with the PageMap? On 5/11/07, Andrew Berman [EMAIL PROTECTED] wrote: I am having a strange issue. If I access my site for the first time (I clear all cookies, sessions, and cache before going to the site), the page comes up fine. However, if I click one of the AJAX links, I get a page expired error. Any thoughts why this is happening? I see it create a new session and the cookie, but it looks like the Ajax link is not valid for some reason. I am using Wicket 1.2.6. Any thoughts? Thanks for any help, Andrew - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user -- View this message in context: http://www.nabble.com/Page-Expiration-when-first-clicking-AJAX-tf3729176.html#a10457848 Sent from the Wicket - User mailing list archive at Nabble.com. - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] Page Expiration when first clicking AJAX
place a breakpoint in: WebRequestCycleProcessor and then line 78: boolean processRequest = true; then look what happens the code should go into: target = resolveRenderedPage(requestCycle, requestParameters); (line 137) Then Session.getPage() is called and that should also return the page.. johan On 5/14/07, Andrew Berman [EMAIL PROTECTED] wrote: I'm willing to try anything to try to workaround or fix this problem. Does anyone have any suggestions where I should start looking or playing around in the Wicket code to figure out possibly what is going on? On 5/13/07, Jonathan Locke [EMAIL PROTECTED] wrote: we're getting some issue like this too and on only one server. Eelco Hillenius wrote: Are you working on multiple servers? On 5/12/07, Andrew Berman [EMAIL PROTECTED] wrote: Igor, Eelco, anyone? This issue is pretty major as I'm losing all the session info when they first come into the app On 5/11/07, Andrew Berman [EMAIL PROTECTED] wrote: Could there be an issue with the PageMap? On 5/11/07, Andrew Berman [EMAIL PROTECTED] wrote: I am having a strange issue. If I access my site for the first time (I clear all cookies, sessions, and cache before going to the site), the page comes up fine. However, if I click one of the AJAX links, I get a page expired error. Any thoughts why this is happening? I see it create a new session and the cookie, but it looks like the Ajax link is not valid for some reason. I am using Wicket 1.2.6. Any thoughts? Thanks for any help, Andrew - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user -- View this message in context: http://www.nabble.com/Page-Expiration-when-first-clicking-AJAX-tf3729176.html#a10457848 Sent from the Wicket - User mailing list archive at Nabble.com. - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] Page Expiration when first clicking AJAX
There is no WebRequestCycleProcessor class in Wicket 1.2.6. On 5/14/07, Johan Compagner [EMAIL PROTECTED] wrote: place a breakpoint in: WebRequestCycleProcessor and then line 78: boolean processRequest = true; then look what happens the code should go into: target = resolveRenderedPage(requestCycle, requestParameters); (line 137) Then Session.getPage() is called and that should also return the page.. johan On 5/14/07, Andrew Berman [EMAIL PROTECTED] wrote: I'm willing to try anything to try to workaround or fix this problem. Does anyone have any suggestions where I should start looking or playing around in the Wicket code to figure out possibly what is going on? On 5/13/07, Jonathan Locke [EMAIL PROTECTED] wrote: we're getting some issue like this too and on only one server. Eelco Hillenius wrote: Are you working on multiple servers? On 5/12/07, Andrew Berman [EMAIL PROTECTED] wrote: Igor, Eelco, anyone? This issue is pretty major as I'm losing all the session info when they first come into the app On 5/11/07, Andrew Berman [EMAIL PROTECTED] wrote: Could there be an issue with the PageMap? On 5/11/07, Andrew Berman [EMAIL PROTECTED] wrote: I am having a strange issue. If I access my site for the first time (I clear all cookies, sessions, and cache before going to the site), the page comes up fine. However, if I click one of the AJAX links, I get a page expired error. Any thoughts why this is happening? I see it create a new session and the cookie, but it looks like the Ajax link is not valid for some reason. I am using Wicket 1.2.6. Any thoughts? Thanks for any help, Andrew - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user -- View this message in context: http://www.nabble.com/Page-Expiration-when-first-clicking-AJAX-tf3729176.html#a10457848 Sent from the Wicket - User mailing list archive at Nabble.com. - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] Page Expiration when first clicking AJAX
Ok, if I paste the jsessionid into the URL for the second request, all works well. ON the third request, it works fine without pasting the jsessionid. How can I append the jsessionid to all requests? On 5/14/07, Andrew Berman [EMAIL PROTECTED] wrote: I've debugged in DefaultRequestTargetResolverStrategy, particularly line 214-215. It looks like when it hits line 214, it's clearly using a brand new session which has none of the information that the original session was holding. Then when it calls Session.getPage(...), it yields a null and hence hits the ExpiredPageClassRequestTarget code. So, for some reason a new session is being created and this seems to be the problem. Could it be what Igor said that the AJAX links don't have the jsessionid in them and this is why it's losing the original session? On 5/14/07, Andrew Berman [EMAIL PROTECTED] wrote: There is no WebRequestCycleProcessor class in Wicket 1.2.6. On 5/14/07, Johan Compagner [EMAIL PROTECTED] wrote: place a breakpoint in: WebRequestCycleProcessor and then line 78: boolean processRequest = true; then look what happens the code should go into: target = resolveRenderedPage(requestCycle, requestParameters); (line 137) Then Session.getPage() is called and that should also return the page.. johan On 5/14/07, Andrew Berman [EMAIL PROTECTED] wrote: I'm willing to try anything to try to workaround or fix this problem. Does anyone have any suggestions where I should start looking or playing around in the Wicket code to figure out possibly what is going on? On 5/13/07, Jonathan Locke [EMAIL PROTECTED] wrote: we're getting some issue like this too and on only one server. Eelco Hillenius wrote: Are you working on multiple servers? On 5/12/07, Andrew Berman [EMAIL PROTECTED] wrote: Igor, Eelco, anyone? This issue is pretty major as I'm losing all the session info when they first come into the app On 5/11/07, Andrew Berman [EMAIL PROTECTED] wrote: Could there be an issue with the PageMap? On 5/11/07, Andrew Berman [EMAIL PROTECTED] wrote: I am having a strange issue. If I access my site for the first time (I clear all cookies, sessions, and cache before going to the site), the page comes up fine. However, if I click one of the AJAX links, I get a page expired error. Any thoughts why this is happening? I see it create a new session and the cookie, but it looks like the Ajax link is not valid for some reason. I am using Wicket 1.2.6. Any thoughts? Thanks for any help, Andrew - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user -- View this message in context: http://www.nabble.com/Page-Expiration-when-first-clicking-AJAX-tf3729176.html#a10457848 Sent from the Wicket - User mailing list archive at Nabble.com. - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net
Re: [Wicket-user] Page Expiration when first clicking AJAX
On 5/14/07, Andrew Berman [EMAIL PROTECTED] wrote: Ok, if I paste the jsessionid into the URL for the second request, all works well. ON the third request, it works fine without pasting the jsessionid. How can I append the jsessionid to all requests? Turn cookie support off at your servlet container. Probably not really what you want, but that should force it for every request. Eelco - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] Page Expiration when first clicking AJAX
Definitely not what I want, but it's the only thing that works. There's clearly a problem in how Wicket is getting the session from the cookie. My Spring MVC app which uses the same WAR has no issues pulling the session info. On 5/14/07, Eelco Hillenius [EMAIL PROTECTED] wrote: On 5/14/07, Andrew Berman [EMAIL PROTECTED] wrote: Ok, if I paste the jsessionid into the URL for the second request, all works well. ON the third request, it works fine without pasting the jsessionid. How can I append the jsessionid to all requests? Turn cookie support off at your servlet container. Probably not really what you want, but that should force it for every request. Eelco - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] Page Expiration when first clicking AJAX
actually wicket does not get session from a cookie, tomcat/servlet container does. -igor On 5/14/07, Andrew Berman [EMAIL PROTECTED] wrote: Definitely not what I want, but it's the only thing that works. There's clearly a problem in how Wicket is getting the session from the cookie. My Spring MVC app which uses the same WAR has no issues pulling the session info. On 5/14/07, Eelco Hillenius [EMAIL PROTECTED] wrote: On 5/14/07, Andrew Berman [EMAIL PROTECTED] wrote: Ok, if I paste the jsessionid into the URL for the second request, all works well. ON the third request, it works fine without pasting the jsessionid. How can I append the jsessionid to all requests? Turn cookie support off at your servlet container. Probably not really what you want, but that should force it for every request. Eelco - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] Page Expiration when first clicking AJAX
Spring MVC does put the jsessionid in the URL. What I don't understand is that when coming into the Wicket app for the first time, it goes to the home page fine with the jsessionid in the URL, and then I click any link and all session attributes are gone. Literally a brand new session is created no matter what link I click. However, once I click that next link, all is fine and that second new session is the one that is used. Just doesn't make any sense. On 5/14/07, Eelco Hillenius [EMAIL PROTECTED] wrote: Definitely not what I want, but it's the only thing that works. There's clearly a problem in how Wicket is getting the session from the cookie. My Spring MVC app which uses the same WAR has no issues pulling the session info. I don't really understand the problem though. Like Johan said, the first time a persistent session is made, Tomcat puts the session id in the URL as it doesn't know yet whether it can rely on cookies (if I understand correctly). Spring MVC might not do that for the particular things you test it for as it doesn't create a session? If you would use stateless pages Wicket wouldn't either. Anyway, there have been discussions about jsessionid on the lists before, and typically it was from people worrying it would mess up search bots etc. If you are worried about that, don't, as bots can filter it. Also, the url is stable as it is not part of the parameters part (which comes after the question mark). It's a universal Java app server thingy, and Wicket has nothing to do with it other than it probably relies on the HttpSession sooner than e.g. model 2 frameworks. Eelco - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] Page Expiration when first clicking AJAX
I think I found the crux of the problem. When you first go to the app, as I've mentioned, it puts the jsessionid in the URL. Well, I compared that sessionid to the one in the cookie created and they are different! That has to be the reason it creates a new session. Now to figure out why it's doing that. On 5/14/07, Andrew Berman [EMAIL PROTECTED] wrote: Spring MVC does put the jsessionid in the URL. What I don't understand is that when coming into the Wicket app for the first time, it goes to the home page fine with the jsessionid in the URL, and then I click any link and all session attributes are gone. Literally a brand new session is created no matter what link I click. However, once I click that next link, all is fine and that second new session is the one that is used. Just doesn't make any sense. On 5/14/07, Eelco Hillenius [EMAIL PROTECTED] wrote: Definitely not what I want, but it's the only thing that works. There's clearly a problem in how Wicket is getting the session from the cookie. My Spring MVC app which uses the same WAR has no issues pulling the session info. I don't really understand the problem though. Like Johan said, the first time a persistent session is made, Tomcat puts the session id in the URL as it doesn't know yet whether it can rely on cookies (if I understand correctly). Spring MVC might not do that for the particular things you test it for as it doesn't create a session? If you would use stateless pages Wicket wouldn't either. Anyway, there have been discussions about jsessionid on the lists before, and typically it was from people worrying it would mess up search bots etc. If you are worried about that, don't, as bots can filter it. Also, the url is stable as it is not part of the parameters part (which comes after the question mark). It's a universal Java app server thingy, and Wicket has nothing to do with it other than it probably relies on the HttpSession sooner than e.g. model 2 frameworks. Eelco - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] Page Expiration when first clicking AJAX
can you debug it some how? Can you figure out why the page is not found? Do you get the second time the same httpsession (that should be created on the first request) johan On 5/13/07, Andrew Berman [EMAIL PROTECTED] wrote: There's two things here: 1. When I click the Ajax link and it doesn't work and the page redirects to the home page, the links are exactly the same 2. When I do a refresh on the browser, the Ajax links are different and there is no jsessionid in the url in the browser. Is this the same problem you posted about? Is there any workaround right now? On 5/12/07, Johan Compagner [EMAIL PROTECTED] wrote: that really looks at the problem i already posted to the dev list, can you compare the pages before and after you refresh the page? look at the urls On 5/12/07, Andrew Berman [EMAIL PROTECTED] wrote: Hey Guys, Thanks for your replies. James: I'll try what you are talking about and see if that fixes the problem. I hope it does Eelco: No multiple servers. I am able to replicate the issue on my local machine as well. Johan: The url coming in is http://localhost/consumer which Wicket auto redirects to /consumer/app/HomePage. However, even if I use the full URL of /consumer/app/HomePage, I still get the issue. You can actually see the issue in action if you go to http://www.cellphonetradeins.com and click, for example, the Cell Phones link on the side. I set the PageExpired page to be the home page, so the page simply refreshes or doesn't work at all. However, when you reload the page and then click the link, it works as desired. So basically, all AJAX links and buttons fail when you first go to the site when you have no cache. You can continue to replicate the issue if you keep clearing your cache and then go to the site again. Thanks again for your help, Andrew On 5/12/07, Johan Compagner [EMAIL PROTECTED] wrote: what is your url you are comming into your app? do you redirect then? What is the final url? johan On 5/12/07, Andrew Berman [EMAIL PROTECTED] wrote: Igor, Eelco, anyone? This issue is pretty major as I'm losing all the session info when they first come into the app On 5/11/07, Andrew Berman [EMAIL PROTECTED] wrote: Could there be an issue with the PageMap? On 5/11/07, Andrew Berman [EMAIL PROTECTED] wrote: I am having a strange issue. If I access my site for the first time (I clear all cookies, sessions, and cache before going to the site), the page comes up fine. However, if I click one of the AJAX links, I get a page expired error. Any thoughts why this is happening? I see it create a new session and the cookie, but it looks like the Ajax link is not valid for some reason. I am using Wicket 1.2.6. Any thoughts? Thanks for any help, Andrew - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - This SF.net email is sponsored by
Re: [Wicket-user] Page Expiration when first clicking AJAX
I've been trying to debug, but am not sure what to really look for. No, I do not get the same session. One is definitely created on the first request and then I see another one created on the second request. On 5/13/07, Johan Compagner [EMAIL PROTECTED] wrote: can you debug it some how? Can you figure out why the page is not found? Do you get the second time the same httpsession (that should be created on the first request) johan On 5/13/07, Andrew Berman [EMAIL PROTECTED] wrote: There's two things here: 1. When I click the Ajax link and it doesn't work and the page redirects to the home page, the links are exactly the same 2. When I do a refresh on the browser, the Ajax links are different and there is no jsessionid in the url in the browser. Is this the same problem you posted about? Is there any workaround right now? On 5/12/07, Johan Compagner [EMAIL PROTECTED] wrote: that really looks at the problem i already posted to the dev list, can you compare the pages before and after you refresh the page? look at the urls On 5/12/07, Andrew Berman [EMAIL PROTECTED] wrote: Hey Guys, Thanks for your replies. James: I'll try what you are talking about and see if that fixes the problem. I hope it does Eelco: No multiple servers. I am able to replicate the issue on my local machine as well. Johan: The url coming in is http://localhost/consumer which Wicket auto redirects to /consumer/app/HomePage. However, even if I use the full URL of /consumer/app/HomePage, I still get the issue. You can actually see the issue in action if you go to http://www.cellphonetradeins.com and click, for example, the Cell Phones link on the side. I set the PageExpired page to be the home page, so the page simply refreshes or doesn't work at all. However, when you reload the page and then click the link, it works as desired. So basically, all AJAX links and buttons fail when you first go to the site when you have no cache. You can continue to replicate the issue if you keep clearing your cache and then go to the site again. Thanks again for your help, Andrew On 5/12/07, Johan Compagner [EMAIL PROTECTED] wrote: what is your url you are comming into your app? do you redirect then? What is the final url? johan On 5/12/07, Andrew Berman [EMAIL PROTECTED] wrote: Igor, Eelco, anyone? This issue is pretty major as I'm losing all the session info when they first come into the app On 5/11/07, Andrew Berman [EMAIL PROTECTED] wrote: Could there be an issue with the PageMap? On 5/11/07, Andrew Berman [EMAIL PROTECTED] wrote: I am having a strange issue. If I access my site for the first time (I clear all cookies, sessions, and cache before going to the site), the page comes up fine. However, if I click one of the AJAX links, I get a page expired error. Any thoughts why this is happening? I see it create a new session and the cookie, but it looks like the Ajax link is not valid for some reason. I am using Wicket 1.2.6. Any thoughts? Thanks for any help, Andrew - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE
Re: [Wicket-user] Page Expiration when first clicking AJAX
maybe because ajax links do not have the jsessionid in them? but then again, the cookie should kick in by second request, so jsessionid in the ajax links is not really necessary. still, passing those urls through request.rewrite() might be something we want to think about. -igor On 5/13/07, Andrew Berman [EMAIL PROTECTED] wrote: I've been trying to debug, but am not sure what to really look for. No, I do not get the same session. One is definitely created on the first request and then I see another one created on the second request. On 5/13/07, Johan Compagner [EMAIL PROTECTED] wrote: can you debug it some how? Can you figure out why the page is not found? Do you get the second time the same httpsession (that should be created on the first request) johan On 5/13/07, Andrew Berman [EMAIL PROTECTED] wrote: There's two things here: 1. When I click the Ajax link and it doesn't work and the page redirects to the home page, the links are exactly the same 2. When I do a refresh on the browser, the Ajax links are different and there is no jsessionid in the url in the browser. Is this the same problem you posted about? Is there any workaround right now? On 5/12/07, Johan Compagner [EMAIL PROTECTED] wrote: that really looks at the problem i already posted to the dev list, can you compare the pages before and after you refresh the page? look at the urls On 5/12/07, Andrew Berman [EMAIL PROTECTED] wrote: Hey Guys, Thanks for your replies. James: I'll try what you are talking about and see if that fixes the problem. I hope it does Eelco: No multiple servers. I am able to replicate the issue on my local machine as well. Johan: The url coming in is http://localhost/consumer which Wicket auto redirects to /consumer/app/HomePage. However, even if I use the full URL of /consumer/app/HomePage, I still get the issue. You can actually see the issue in action if you go to http://www.cellphonetradeins.com and click, for example, the Cell Phones link on the side. I set the PageExpired page to be the home page, so the page simply refreshes or doesn't work at all. However, when you reload the page and then click the link, it works as desired. So basically, all AJAX links and buttons fail when you first go to the site when you have no cache. You can continue to replicate the issue if you keep clearing your cache and then go to the site again. Thanks again for your help, Andrew On 5/12/07, Johan Compagner [EMAIL PROTECTED] wrote: what is your url you are comming into your app? do you redirect then? What is the final url? johan On 5/12/07, Andrew Berman [EMAIL PROTECTED] wrote: Igor, Eelco, anyone? This issue is pretty major as I'm losing all the session info when they first come into the app On 5/11/07, Andrew Berman [EMAIL PROTECTED] wrote: Could there be an issue with the PageMap? On 5/11/07, Andrew Berman [EMAIL PROTECTED] wrote: I am having a strange issue. If I access my site for the first time (I clear all cookies, sessions, and cache before going to the site), the page comes up fine. However, if I click one of the AJAX links, I get a page expired error. Any thoughts why this is happening? I see it create a new session and the cookie, but it looks like the Ajax link is not valid for some reason. I am using Wicket 1.2.6. Any thoughts? Thanks for any help, Andrew - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - This SF.net email is sponsored by DB2 Express Download DB2 Express C
Re: [Wicket-user] Page Expiration when first clicking AJAX
we're getting some issue like this too and on only one server. Eelco Hillenius wrote: Are you working on multiple servers? On 5/12/07, Andrew Berman [EMAIL PROTECTED] wrote: Igor, Eelco, anyone? This issue is pretty major as I'm losing all the session info when they first come into the app On 5/11/07, Andrew Berman [EMAIL PROTECTED] wrote: Could there be an issue with the PageMap? On 5/11/07, Andrew Berman [EMAIL PROTECTED] wrote: I am having a strange issue. If I access my site for the first time (I clear all cookies, sessions, and cache before going to the site), the page comes up fine. However, if I click one of the AJAX links, I get a page expired error. Any thoughts why this is happening? I see it create a new session and the cookie, but it looks like the Ajax link is not valid for some reason. I am using Wicket 1.2.6. Any thoughts? Thanks for any help, Andrew - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user -- View this message in context: http://www.nabble.com/Page-Expiration-when-first-clicking-AJAX-tf3729176.html#a10457848 Sent from the Wicket - User mailing list archive at Nabble.com. - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] Page Expiration when first clicking AJAX
Are you working on multiple servers? On 5/12/07, Andrew Berman [EMAIL PROTECTED] wrote: Igor, Eelco, anyone? This issue is pretty major as I'm losing all the session info when they first come into the app On 5/11/07, Andrew Berman [EMAIL PROTECTED] wrote: Could there be an issue with the PageMap? On 5/11/07, Andrew Berman [EMAIL PROTECTED] wrote: I am having a strange issue. If I access my site for the first time (I clear all cookies, sessions, and cache before going to the site), the page comes up fine. However, if I click one of the AJAX links, I get a page expired error. Any thoughts why this is happening? I see it create a new session and the cookie, but it looks like the Ajax link is not valid for some reason. I am using Wicket 1.2.6. Any thoughts? Thanks for any help, Andrew - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] Page Expiration when first clicking AJAX
what is your url you are comming into your app? do you redirect then? What is the final url? johan On 5/12/07, Andrew Berman [EMAIL PROTECTED] wrote: Igor, Eelco, anyone? This issue is pretty major as I'm losing all the session info when they first come into the app On 5/11/07, Andrew Berman [EMAIL PROTECTED] wrote: Could there be an issue with the PageMap? On 5/11/07, Andrew Berman [EMAIL PROTECTED] wrote: I am having a strange issue. If I access my site for the first time (I clear all cookies, sessions, and cache before going to the site), the page comes up fine. However, if I click one of the AJAX links, I get a page expired error. Any thoughts why this is happening? I see it create a new session and the cookie, but it looks like the Ajax link is not valid for some reason. I am using Wicket 1.2.6. Any thoughts? Thanks for any help, Andrew - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] Page Expiration when first clicking AJAX
Hey Guys, Thanks for your replies. James: I'll try what you are talking about and see if that fixes the problem. I hope it does Eelco: No multiple servers. I am able to replicate the issue on my local machine as well. Johan: The url coming in is http://localhost/consumer which Wicket auto redirects to /consumer/app/HomePage. However, even if I use the full URL of /consumer/app/HomePage, I still get the issue. You can actually see the issue in action if you go to http://www.cellphonetradeins.com and click, for example, the Cell Phones link on the side. I set the PageExpired page to be the home page, so the page simply refreshes or doesn't work at all. However, when you reload the page and then click the link, it works as desired. So basically, all AJAX links and buttons fail when you first go to the site when you have no cache. You can continue to replicate the issue if you keep clearing your cache and then go to the site again. Thanks again for your help, Andrew On 5/12/07, Johan Compagner [EMAIL PROTECTED] wrote: what is your url you are comming into your app? do you redirect then? What is the final url? johan On 5/12/07, Andrew Berman [EMAIL PROTECTED] wrote: Igor, Eelco, anyone? This issue is pretty major as I'm losing all the session info when they first come into the app On 5/11/07, Andrew Berman [EMAIL PROTECTED] wrote: Could there be an issue with the PageMap? On 5/11/07, Andrew Berman [EMAIL PROTECTED] wrote: I am having a strange issue. If I access my site for the first time (I clear all cookies, sessions, and cache before going to the site), the page comes up fine. However, if I click one of the AJAX links, I get a page expired error. Any thoughts why this is happening? I see it create a new session and the cookie, but it looks like the Ajax link is not valid for some reason. I am using Wicket 1.2.6. Any thoughts? Thanks for any help, Andrew - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] Page Expiration when first clicking AJAX
There's two things here: 1. When I click the Ajax link and it doesn't work and the page redirects to the home page, the links are exactly the same 2. When I do a refresh on the browser, the Ajax links are different and there is no jsessionid in the url in the browser. Is this the same problem you posted about? Is there any workaround right now? On 5/12/07, Johan Compagner [EMAIL PROTECTED] wrote: that really looks at the problem i already posted to the dev list, can you compare the pages before and after you refresh the page? look at the urls On 5/12/07, Andrew Berman [EMAIL PROTECTED] wrote: Hey Guys, Thanks for your replies. James: I'll try what you are talking about and see if that fixes the problem. I hope it does Eelco: No multiple servers. I am able to replicate the issue on my local machine as well. Johan: The url coming in is http://localhost/consumer which Wicket auto redirects to /consumer/app/HomePage. However, even if I use the full URL of /consumer/app/HomePage, I still get the issue. You can actually see the issue in action if you go to http://www.cellphonetradeins.com and click, for example, the Cell Phones link on the side. I set the PageExpired page to be the home page, so the page simply refreshes or doesn't work at all. However, when you reload the page and then click the link, it works as desired. So basically, all AJAX links and buttons fail when you first go to the site when you have no cache. You can continue to replicate the issue if you keep clearing your cache and then go to the site again. Thanks again for your help, Andrew On 5/12/07, Johan Compagner [EMAIL PROTECTED] wrote: what is your url you are comming into your app? do you redirect then? What is the final url? johan On 5/12/07, Andrew Berman [EMAIL PROTECTED] wrote: Igor, Eelco, anyone? This issue is pretty major as I'm losing all the session info when they first come into the app On 5/11/07, Andrew Berman [EMAIL PROTECTED] wrote: Could there be an issue with the PageMap? On 5/11/07, Andrew Berman [EMAIL PROTECTED] wrote: I am having a strange issue. If I access my site for the first time (I clear all cookies, sessions, and cache before going to the site), the page comes up fine. However, if I click one of the AJAX links, I get a page expired error. Any thoughts why this is happening? I see it create a new session and the cookie, but it looks like the Ajax link is not valid for some reason. I am using Wicket 1.2.6. Any thoughts? Thanks for any help, Andrew - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] Page Expiration when first clicking AJAX
I have an issue with links and page expiration about which I posted a jira entry here: https://issues.apache.org/jira/browse/WICKET-557 I haven't the least idea about whether this is related or not to your problem. Cheers, Carlos On 5/12/07, Andrew Berman [EMAIL PROTECTED] wrote: There's two things here: 1. When I click the Ajax link and it doesn't work and the page redirects to the home page, the links are exactly the same 2. When I do a refresh on the browser, the Ajax links are different and there is no jsessionid in the url in the browser. Is this the same problem you posted about? Is there any workaround right now? On 5/12/07, Johan Compagner [EMAIL PROTECTED] wrote: that really looks at the problem i already posted to the dev list, can you compare the pages before and after you refresh the page? look at the urls On 5/12/07, Andrew Berman [EMAIL PROTECTED] wrote: Hey Guys, Thanks for your replies. James: I'll try what you are talking about and see if that fixes the problem. I hope it does Eelco: No multiple servers. I am able to replicate the issue on my local machine as well. Johan: The url coming in is http://localhost/consumer which Wicket auto redirects to /consumer/app/HomePage. However, even if I use the full URL of /consumer/app/HomePage, I still get the issue. You can actually see the issue in action if you go to http://www.cellphonetradeins.com and click, for example, the Cell Phones link on the side. I set the PageExpired page to be the home page, so the page simply refreshes or doesn't work at all. However, when you reload the page and then click the link, it works as desired. So basically, all AJAX links and buttons fail when you first go to the site when you have no cache. You can continue to replicate the issue if you keep clearing your cache and then go to the site again. Thanks again for your help, Andrew On 5/12/07, Johan Compagner [EMAIL PROTECTED] wrote: what is your url you are comming into your app? do you redirect then? What is the final url? johan On 5/12/07, Andrew Berman [EMAIL PROTECTED] wrote: Igor, Eelco, anyone? This issue is pretty major as I'm losing all the session info when they first come into the app On 5/11/07, Andrew Berman [EMAIL PROTECTED] wrote: Could there be an issue with the PageMap? On 5/11/07, Andrew Berman [EMAIL PROTECTED] wrote: I am having a strange issue. If I access my site for the first time (I clear all cookies, sessions, and cache before going to the site), the page comes up fine. However, if I click one of the AJAX links, I get a page expired error. Any thoughts why this is happening? I see it create a new session and the cookie, but it looks like the Ajax link is not valid for some reason. I am using Wicket 1.2.6. Any thoughts? Thanks for any help, Andrew - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Wicket-user mailing list
Re: [Wicket-user] Page Expiration when first clicking AJAX
Could there be an issue with the PageMap? On 5/11/07, Andrew Berman [EMAIL PROTECTED] wrote: I am having a strange issue. If I access my site for the first time (I clear all cookies, sessions, and cache before going to the site), the page comes up fine. However, if I click one of the AJAX links, I get a page expired error. Any thoughts why this is happening? I see it create a new session and the cookie, but it looks like the Ajax link is not valid for some reason. I am using Wicket 1.2.6. Any thoughts? Thanks for any help, Andrew - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] Page Expiration when first clicking AJAX
Igor, Eelco, anyone? This issue is pretty major as I'm losing all the session info when they first come into the app On 5/11/07, Andrew Berman [EMAIL PROTECTED] wrote: Could there be an issue with the PageMap? On 5/11/07, Andrew Berman [EMAIL PROTECTED] wrote: I am having a strange issue. If I access my site for the first time (I clear all cookies, sessions, and cache before going to the site), the page comes up fine. However, if I click one of the AJAX links, I get a page expired error. Any thoughts why this is happening? I see it create a new session and the cookie, but it looks like the Ajax link is not valid for some reason. I am using Wicket 1.2.6. Any thoughts? Thanks for any help, Andrew - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] Page expiration
the ajax stuff is still a work in progress, and the expiration issue is something that remains to be solved. the problem is that each request creates a new version of the page and so if you use any non-ajax link it will calse the page expired page since the link points to an older version of the page. one way around it currently is to turn off versioning on the page. -Igor On 2/3/06, Mark Derricutt [EMAIL PROTECTED] wrote: Hey all,I've started playing with AjaxSelfUpdatingTimerBehavior's in my simple wicket application (CVS snapshot of Wicket ~1day old) and noticed some odd behaviour:The moment the AJAX update occurs, if I submit any forms on the page, I get redirected to a Page Expired page. Is this configurable? I can imagine a page being expired if a session timed out, but this is only like after 5 seconds. I'm running my application from the Firefox sidebar, the default Page Expired page has a link to Return to home page which loads the home page in tthe first firefox tab, not the side bar. There doesn't seem to be any target's on the HREF so I'm not sure why its opening in the main page :( Any ideas? If I add an AjaxSelfUpdatingTimerBehavior behaviour to a Label thats part of a ListView, wicket crashes out, I tried adding a MarkupIdSetter.INSTANCE behaviour like I've seen in the Ajax clock example but no joy. wicket.WicketRuntimeException: Unable to determine markup for component: [Component id = activityTime, page = wicket.quickstart.Index, path = 0:activities:0:activityTime.Label, isVisible = true, isVersioned = true] at wicket.Component.getMarkupId(Component.java:690) at wicket.ajax.AjaxSelfUpdatingTimerBehavior.onComponentTag(AjaxSelfUpdatingTimerBehavior.java:50) at wicket.behavior.AbstractAjaxBehavior.onComponentTag (AbstractAjaxBehavior.java:146)Any one got any ideas?PS: Loving the simplicity of the AJAX behaviors - very nice.-- i like my video games - mamma said they are gonna melt my brains i like my video games - i don't care what daddy said; they're my reality- henning pauly
Re: [Wicket-user] Page Expiration
oh, and yes, the only way to never have timeouts is to use bookmarkable page links as bookmarkable pages do not use a prior session (in fact, if you don't have a session yet and you navigate to a bookmarkable page, a new session is created). Eelco On 11/1/05, Eelco Hillenius [EMAIL PROTECTED] wrote: It your session that timed out. You can configure it as part of web.xml. Eelco On 11/1/05, Dan Gould [EMAIL PROTECTED] wrote: If I load a wicket page that contains some PageLinks, then I walk away for awhile and then come back and click on one of the links, I get sent to the Page Expired page. (I haven't restarted the server or hit any other pages in the meantime). I'm probably missing something obvious, but I'm not sure how to avoid this (other than using BookmarkablePageLinks everywhere, but that won't help with forms). Am I misusing detatchable models somehow? Is there a way to save state? Is there a way to change the timeout that I'm missing? Is it a tomcat issue? Thank you very much (for this and all the help on the list), Dan --- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42 plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user --- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42 plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
