> Well, the AbstractContainer implementation never > releases its services. Design flaw?
I noticed this some days ago. I first thought that this was not a problem as (in my thinking) the container was the first thing created and the last destroyed. In that, the undisposed services of the container will go away with the container itself. But, if one of those services book an external resource (which is not the case for now - heu i don't for instrument...) this would cause an unreleased resource. Moreover, the recent discussion about containers in containers (with Fortress) clearly indicates that this should be fixed. Cheers, A+. Didier. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
