Ok, I`m using jsf and have managed beans with session scope and
properties other managed beans. Most of them have application scoped
beans references as properties, which makes connection to DB...and...
these fields are defined as transient to prevent serialization.
eg.
class TestBean implements
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Stanimir,
On 2/11/2009 10:10 AM, Stanimir Komitov wrote:
when the application is restarted, the session scoped beans are
serialized on stop and restored on requesting the same session after
start, but when the class is deserialized, transient
Hi,
How to exclude some classes to being serialized in sharing session with
clustered tomcats?
I`m using hibernate, spring, java mail, apache commons dbcp, pool ...
and to serialize/deserialize sessions all the classes must implement
Serializable (or Externalizable), and I think that it`s not a
Stanimir Komitov wrote:
Hi,
How to exclude some classes to being serialized in sharing session with
clustered tomcats?
I`m using hibernate, spring, java mail, apache commons dbcp, pool ...
and to serialize/deserialize sessions all the classes must implement
Serializable (or
Dear Stanimir,
How to exclude some classes to being serialized in sharing session
with
clustered tomcats?
I`m using hibernate, spring, java mail, apache commons dbcp, pool ...
and to serialize/deserialize sessions all the classes must implement
Serializable (or Externalizable), and I think
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Stanimir,
On 2/10/2009 11:25 AM, Stanimir Komitov wrote:
How to exclude some classes to being serialized in sharing session with
clustered tomcats?
Do you mean avoiding serializing some /objects/ in shared sessions?
I can see your problem. You
