I'm not trying to - I only put the serialization code in as a protection
from my bean being "reset". Originally I put in no serialization code as I
was assured that the server would not be reset and that my application bean
should exist for the duration of the application. It was, however,
regularly reset so I put in the serialization. This made no difference. It
still gets reset.
Paul
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
Behalf Of Geir Magnusson Jr.
Sent: 28 June 2001 13:10
To: [EMAIL PROTECTED]
Subject: Re: Tomcat and Beans
Paul Hunnisett wrote:
>
> How does Tomcat manage standard Java beans? I have attempted to use an
> application scoped bean ands have included serialization code in the
> finalize() method and the code to read up from file in the constructor. I
> assumed that whenever Tomcat thought a bean was unnecesary it would simply
> garbage collect it(which would call my finalize() method) but this doesn't
> seem to happen. The bean get's created fine, but not serialized properly.
> What is Tomcat doing?
How do you ensure that the bean is no longer referenced?
--
Geir Magnusson Jr. [EMAIL PROTECTED]
System and Software Consulting
Developing for the web? See http://jakarta.apache.org/velocity/
You have a genius for suggesting things I've come a cropper with!
