Michal Glowacki wrote:
No, I don't store bean in static variable (and it's not when 'back' is
pressed :-) ). The code was unchanged and was working ok some time ago.
That's why I've started to think it could be Tomcat issue.
The problem should be this (from server logs, when web-app is accessed
for the first time after deploy)
07:57:07,953 INFO [ServletCacheAdministrator] Created new instance of
ServletCacheAdministrator
07:57:07,953 INFO [ServletCacheAdministrator] Created new
application-scoped cache at key: __oscache_cache
Looks like OSCache library, but I never added anything to descriptors
which uses cache. But I put oscache.jar into jsf-lib directory, as
ajax4jsf library needs it.
Could it be the problem?
yes, looks like it's caching the bean in the page once changes have been
made to the bean it remembers them.
Regards,
Michal
----- Original Message ----- From: "Pid" <[EMAIL PROTECTED]>
To: "Tomcat Users List" <users@tomcat.apache.org>
Sent: Thursday, March 01, 2007 11:15 AM
Subject: Re: page remembers data
(Please reply to the list only, I don't need to get the message twice.)
I'm assuming you're not clicking back to get there, but if it's not
your browser then it sounds like you aren't initialising the bean
properly.
Have you stored the bean in a static variable?
Can you change the code of the beans to log what happens when they're
changed or called?
p
Michal Glowacki wrote:
Yes, for sure. I've flushed browser cache and didn't help. Checked in
FF and IE.
Regards,
Michal
----- Original Message ----- From: "Pid" <[EMAIL PROTECTED]>
To: "Tomcat Users List" <users@tomcat.apache.org>
Sent: Thursday, March 01, 2007 8:47 AM
Subject: Re: page remembers data
Michal Glowacki wrote:
Hi
I'm not sure if it's the problem of Tomcat, but I've spotted it
after
upgrading to JBoss 4.0.5 (Tomcat 5.5.20). This not the problem of
session
scoped beans as I'm using request ones. When I enter some data,
submit them
and return back to that page, the data remains there. I've no clue
why it's
like this. Has anyone idea what can be the problem?
sure it's the page and not the browser?
Regards,
Michal
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
