Ahh, i thought you meant the *container* was getting reset =)
Hmm... interesting. I've used application-scoped beans before, just by
useBean'ing them to application scope. I can see where conceptually one
would think they're getting reset (that multiple useBeans referring to the
same application-scoped bean would cause it to overwrite the one already
created) but that wasn't the behavior I saw in 3.2.1.
- r
> -----Original Message-----
> From: Paul Hunnisett [mailto:[EMAIL PROTECTED]]
> Sent: June 28, 2001 8:27 AM
> To: [EMAIL PROTECTED]
> Subject: RE: Tomcat and Beans
>
>
> The application is not being shut down! Yet somehow my beans
> are getting
> "reset".
>
> Paul
>
> -----Original Message-----
> From: Robert Slifka [mailto:[EMAIL PROTECTED]]
> Sent: 28 June 2001 13:26
> To: '[EMAIL PROTECTED]'
> Subject: RE: Tomcat and Beans
>
>
> >From "The Java Programming Language, 3rd. Ed"
>
> "When an application exits, no further GC is performed, so
> any objects that
> have not yet been collected will not have their finalize()
> methods invoked."
>
> - r
>
> > -----Original Message-----
> > From: Paul Hunnisett [mailto:[EMAIL PROTECTED]]
> > Sent: June 28, 2001 8:19 AM
> > To: [EMAIL PROTECTED]
> > Subject: RE: Tomcat and Beans
> >
> >
> > 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!
> >
> >
>
>
