Hi,
Friday, November 19, 2004, 8:27:49 PM, you wrote:
> process of elimination should be pretty straightforward on this then...
> i'd say, grep for session and cookie in wicket and put print statements
> right before each thing that invalidates the session. run the thing
> until things go wrong,
Juergen sent me a stripped down example that did not
show the bug. I replaced his HTML with the attached
HTML to reproduce the bug.
Next I will dig up the email that juergen sent me and
forward that as well. Then you can combine them.
-geoff
__
when you get a fairly minimal repro case, please send it my way.
Geoff hendrey wrote:
It happens on both Jetty and Tomcat.
The "page expired" will occur when, for example,
repeatedly clicking on different items from a dropdown
that cause submission and page update.
Sometimes it's 10 clicks, sometim
process of elimination should be pretty straightforward on this then...
i'd say, grep for session and cookie in wicket and put print statements
right before each thing that invalidates the session. run the thing
until things go wrong, then look at the output. if there's output, the
problem ha
It happens on both Jetty and Tomcat.
The "page expired" will occur when, for example,
repeatedly clicking on different items from a dropdown
that cause submission and page update.
Sometimes it's 10 clicks, sometimes 40. Sometimes 2.
Never 1.
I've been very systematic. I'll do a "ripdown" to cut
2) I explicitly set session-timeout to minutes. Sometimes the error
occurs after the second selection, sometime only after the 10 and sometimes
not at all.
1) Jetty 4.2.11, Jetty 5.0.0 and Tomcat 5.0.27
Regards
Juergen
-Ursprüngliche Nachricht-
Von: [EMAIL PROTECTED]
[mailto:[EMA
"The trace reveals also that suddenly a new JSESSION cookie is set."
this does not sound like a wicket problem. it sounds like an app
container problem to me.
two questions:
1. does this problem occur in more than one servlet environment?
2. what timeout value is set for session expiration?
Donn
Hi Juergen,
Friday, November 19, 2004, 2:27:18 PM, you wrote:
> Summary on the "page expiry" problem:
Thanks - Do you have any sources that show the problem that I could
grab?
--
Best regards,
Gwynmailto:[EMAIL PROTECTED]
Summary on the "page expiry" problem:
=
I'm still trying to figure out what you stale exception causes. What I know
for sure by now is, that it has something to do with the Session object. I
don't yet know why, but it new one gets assigned from time to time, without
obvious rea
Do you have a summary of the current state of the problem, as I'm
afraid I've lost track with the different threads you're creating.
On Fri, 19 Nov 2004 08:02:44 +0100, Donnerstag, Juergen
<[EMAIL PROTECTED]> wrote:
> Geoff,
>
> It'd be really unfortunate to loose you. I'll try to encourage some
You can find the jars you need in the /lib dir of Wicket/ Wicket
examples/ ... If they cannot be downloaded from a external repository,
you can create the needed entries yourself.
The default location of the repository is {user_home}/.maven/repository.
A statement like:
ognl
For generating an ant build script, you can just type: 'maven ant'.
Eelco
Jonathan Locke wrote:
any maven experts out there?
what are the failures below about?
if i'm building my own project using the examples maven project.xml as
a template, how do i generate an ant build script?
thanks!
12 matches
Mail list logo