Yes, it might be the same problem I had with the serialization.
Could you maybe paste your stack trace and let me know the JIRA id, so I can
track it.
You mentioned you had an other configuration which the HttpSessionStore.
What is this and how can it be enabled ?
Thanks,
Carsten
Victor
Hi,
I setup our wicket application on a simple JBoss cluster with session
replication.
Doing that I get more or less immediately the following track trace: (I
paste only the upper part, but the same message gets repeated over and over
in the stack trace)
I use wicket 1.3.4, but it's the same
.
One of the main reasons for this is that if you don't, your page won't
work
properly when you click a link that modifies something on the page -
because
it doesn't reconstruct the page, and therefore you don't refresh the
data
in
your components.
On Wed, Jan 14, 2009 at 11:09 AM, behrica
Hello,
I do something similar in a page constructor, even with accessing the
service layer. I have the same concerns, if this is correct. In general I do
not like if a constructor does any significant (eventually time consuming)
work like database access or other. But I did not find an other
