I've been seeing similar exceptions, but haven't investigated in
depth. They've only been hitting the administrative pages on my site,
which makes me think that it's due to a combination of tabbed browsing
and expired pages. Forgive my vagueness... I haven't looked closely
at wicket's internals.
My theory...
1. User loads page A in a tab with form "foo" on it. Page has id 1 in
the pagemap.
2. Time passes, session/pagemap expires.
3. User loads page B in another tab. It also gets id 1.
4. User returns to tab A and submits form "foo". Wicket complains
because there is no component "foo" in page B.
I tried enabling multi-tab support to see if that would help, but it
didn't work with my mounted URLs. I've read that using
HybridUrlEncoding (?) could resolve that problem, but the problem
hasn't been wide-spread enough to justify the risk.
Hope this helps,
Alex
On Aug 4, 2008, at 2:25 PM, Jeremy Levy wrote:
We have been struggling with an issue for several months now, any
help would
be appreciated. In our logs I see variations of the same error on the
following error which results in a 500 for the user:
2008-08-04 13:21:24,006 ERROR Wap [RequestCycle] : component
updateSection:theForm not found on page
com.mdate.wap.messagecenter.TypeChatPage[id = 7], listener interface =
[RequestListenerInterface name=IFormSubmitListener, method=public
abstract
void
org
.apache.wicket.markup.html.form.IFormSubmitListener.onFormSubmitted()]
org.apache.wicket.WicketRuntimeException: component
updateSection:theForm
not found on page com.mdate.wap.messagecenter.TypeChatPage[id = 7],
listener
interface = [RequestListenerInterface name=IFormSubmitListener,
method=public abstract void
org
.apache.wicket.markup.html.form.IFormSubmitListener.onFormSubmitted()]
at
org
.apache
.wicket
.request
.AbstractRequestCycleProcessor
.resolveListenerInterfaceTarget(AbstractRequestCycleProcessor.java:
416)
[snip]
We are unable to repeat the issue and the pages render correctly
when we
test them. There is no AJAX in use on this site, and I can't
identify any
specific pattern. The error happens on unauthenticated pages as
well as
authenticated pages. We are using Wicket 1.3.4. The components
that are
referenced in the error messages don't exist on pages the messages
reference.
J
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
