Can you create a failing test to reproduce this? Also, if sobj1 is an optional dependency of tobj1, it should probably be modeled as a property, not as a ctor arg... On 2011 7 19 11:39, "mynkow" <myn...@gmail.com> wrote: > Hi > > I have a transient object *TObj1 *which depends on singleton object SObj1.
> SObj1 is supposed to be UP in 99.99% of the application life time. Now I am > in a situation where the singleton cannot be created. If that happens I set > SObj1 = null in TObj1's ctor when I try to resolve an instance of TObj1. > When I try to release TObj1 (because it is transient) I got a Castle > exception that parameter "*instance*" cannot be null. The only thing that is > null is SObj1. As far as I know singleton objects cannot be released. They > are "destroyed" when we "destroy" the container. Then Why castle windsor > actually tries to release the singleton? Is there any way to release only > the transient? > > -- > You received this message because you are subscribed to the Google Groups "Castle Project Users" group. > To view this discussion on the web visit https://groups.google.com/d/msg/castle-project-users/-/KtfSwkD21a0J. > To post to this group, send email to castle-project-users@googlegroups.com . > To unsubscribe from this group, send email to castle-project-users+unsubscr...@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/castle-project-users?hl=en. > -- You received this message because you are subscribed to the Google Groups "Castle Project Users" group. To post to this group, send email to castle-project-users@googlegroups.com. To unsubscribe from this group, send email to castle-project-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/castle-project-users?hl=en.
