I'm not sure either - I don't see why it would be like that so I tried imagining why the code was written like that. The only thing I could come up with is that if a parent handler was used to resolve a component, then the child disposed, the parent might keep the component burden around.
-r 2012/2/9 Krzysztof Koźmic <[email protected]> > Hi Rory, > > so what would you expect it to do? > Not sure I understand the part about burdens. Do you think you could > reproduce it in a failing test? > > @K > > > On 10/02/2012 7:02 AM, Rory Plaire wrote: > > The implementation of IDisposable.Dispose in calls the protected Dispose > which looks like this: > > > protected virtual void Dispose(bool disposing) > { > if (disposing) > { > if (parentHandler != null) > { > } > } > } > > > Was there an intention to do more there? Would the parent handler leak > Burden instances if components were resolved and then the handler get > disposed? > > -r > -- > You received this message because you are subscribed to the Google Groups > "Castle Project Development List" 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-devel?hl=en. > > > -- > You received this message because you are subscribed to the Google Groups > "Castle Project Development List" 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-devel?hl=en. > -- You received this message because you are subscribed to the Google Groups "Castle Project Development List" 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-devel?hl=en.
