> So be careful if you have dependencies like me. Windsor is not giving any detailed info about registered but not initialized components. It seems only collecting resolution conflicts and gaps. Any initialization or chain based mistakes will be welcomed in a dark room :)
If you can could you put together a unit test for this scenario, we've already got quite a few unit tests for unsatisfied dependencies so it would be good to get this defect in error reporting fixed. A pull request with a unit test would be great. On Wed, Dec 6, 2017 at 2:46 AM Doruk Dalçam <[email protected]> wrote: > After trying all the solutions nearly 8 hours I initialized all types and > subtypes in the project. And change initialization order. Then I found > there is a dependency JConnector<T> of T so I registered all T's and > initialized aaand voila! > > So be careful if you have dependencies like me. Windsor is not giving any > detailed info about registered but not initialized components. It seems > only collecting resolution conflicts and gaps. Any initialization or chain > based mistakes will be welcomed in a dark room :) > > Have a nice day. > > -- > 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 [email protected]. > To post to this group, send email to [email protected] > . > Visit this group at https://groups.google.com/group/castle-project-users. > For more options, visit https://groups.google.com/d/optout. > -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/castle-project-users. For more options, visit https://groups.google.com/d/optout.
