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 Expire
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
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 th
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 doin
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
se
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
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
the cookie is created using the servlet container.i am not sure why it would
create a new one. the only thing i can think of is that if there are two
parallel "first" requests that come in. one sets cookie A, and the other
sets cookie B and overrides A? but this problem should be solved by the
ser
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 i
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 H
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
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 i
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 f
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 whe
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 sess
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
d
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
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 fir
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 d
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
> 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,
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
Sp
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,
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 servle
Ok, well the only solution I've found is to disable cookies in Tomcat.
Works as desired, but the jsessionid is in every url.
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 fi
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 DefaultRequestTargetReso
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
hen
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(reque
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..
joha
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 lik
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 com
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, And
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
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 does
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 tw
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
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 se
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
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
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
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 strang
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 l
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
sess
43 matches
Mail list logo
