Hello

Whenever I access cocoon2.2 beans via context.getBean(component.ROLE),
do I have to respect a few lifecycle contracts, like
release(component) like I used to do with cocoonComponentManager under
2.1, perhaps something like calling bean destroy() method once I'm
done with them, and init() them back later ?

I'm worrying about letting unused components fill up my memory space,
unless of course the new container cleanups everything in the
background.

Thanks !

laurent

--
<a href="http://in-pocket.blogspot.com";>http://in-pocket.blogspot.com
- Mobile world, technology and more</a>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to