Hi,
I'm using wicket 6.6.
thanks,
Giovanni
Il 08/05/13 12:52, Giovanni Cuccu ha scritto:
Hi,
I'm facing a random error and I'm not able to trace its cause.
The error is
'could not find component x on page y error'
The problem is that the component named x has never been on page y.
The component name reported in the error is an old one (which is not
in the jar app anymore) and it was orginally on another page.
I did delete the filestore files in the last deploy so I don't know
where the app is taking the reference to x component.
I have no ajax replace on the page y and there waere no ajax replace
on the original page either.
The user actions are the following
the user tries to load the app using an url that point to a protected
(i.e required login) page
the page being requested is expired
the user get redirect to a login page
the user does some operations successfully
the user "sleeps" for the session expiration period
the user select a page anf got the error
I have a special Logback logger that put the logging events (SLF4J) of
a single logged user into a thread local variable and on error it
dumps a file; I don't know it this can be related to the error, so I
put it on the table.
Can anyone suggest a way to find the cause of this error?
Thanks,
Giovanni
--
Giovanni Cuccu
Responsabile area sviluppo - CUP 2000 Spa
Via del Borgo di S. Pietro, 90/c - 40126 Bologna
e-mail: giovanni.cuccu _at_ cup2000.it
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
