if you resolve it, you should release it. that's the rule i follow. as for tracking. disposable objects are just one kind of tracking. they are known as Burden. DisposableBurden is the most common, but there are others. This is where the memory leak can come from if you do not properly release the component from the kernel. there may be other extension points that could potentially leak as well, (de)commission concerns and the like. But i'm not 100% sure about those.
-- You received this message because you are subscribed to the Google Groups "Castle Project Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/castle-project-users?hl=en.
