Hi, We are using the startable facility first to start components (:)) but also because i thought it would allow us to postpone some actions after a complete initialization.
We get a "strange" behaviour: - when a startable singleton A is started (Start()), it invokes an injected component B - B also needs a reference to A and calls Resolve<A>() to get it What happens is that a second instance of A is created and started. Why ? I know that A could give a reference of itself to B but ... i would like to understand the startable feature et what goes wrong. thks Xavier -- 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.
