On Thursday 21 February 2002 10:26 am, Torsten Curdt wrote: > > Isn't this basically a SingleThreaded component? Where every time one is > > requested from the CM a new instance is created? > > Yes... seems you are right. But do I have to release it?
Not really :) When you release a SingleThreaded component, it will only call stop() and dispose() if the component is Startable and Disposable respectively. Since you wrote your component, as long as it doesn't lock onto any resources for its entire lifespan you could get away with not releasing it at all. Otherwise if it is holding onto something that should be released, (or for completeness) you could implement a HttpSessionListener (or whatever the name was...) and just have it check for Startable and Disposable and call if needed. Personally, I'd just stick it in the session, make sure I don't latch onto any poolable resources for the life of my component :) -pete -- peter royal -> [EMAIL PROTECTED] -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
