Actually that is how it was implemented. I've started refactoring since I need to perform some activities before dispose - in fact each component controlled by the manager manages process, on dispose manager has to communicate with all the processes collect some data write aggregated info to log and so on. (I'm working on application server) I've created stop method in manager and colling it before disposing container as workaround (going to convert it to stop concern )
I'm just wondering is the behaviour I've described in my first message correct or it is a bug... If it is a bug I'll put a task to issue tracker to refactore the code once new version of windsor with fix is available. On Monday, September 30, 2013 1:27:45 AM UTC+4, Krzysztof Koźmic wrote: > > both the manager and factory are singleton. > > In that case I'd remove the Dispose method from the manager - it doesn't > do anything the container won't itself do anyway > > -- > Krzysztof Kozmic > > On Monday, 30 September 2013 at 3:37 AM, Konstantin wrote: > > Any update? > > -- > You received this message because you are subscribed to the Google Groups > "Castle Project Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to castle-project-users+unsubscr...@googlegroups.com <javascript:>. > To post to this group, send email to > castle-pro...@googlegroups.com<javascript:> > . > Visit this group at http://groups.google.com/group/castle-project-users. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- You received this message because you are subscribed to the Google Groups "Castle Project Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to castle-project-users+unsubscr...@googlegroups.com. To post to this group, send email to castle-project-users@googlegroups.com. Visit this group at http://groups.google.com/group/castle-project-users. For more options, visit https://groups.google.com/groups/opt_out.
