I know what mandatory and optional args are and how they are used. The issue here is that Resolve<T>(IDictionary) can override optional args, but not mandatory args. I think that is at least an unexpected behavior if not a bug.
On Jul 10, 8:18 am, Jason Meckley <[email protected]> wrote: > ctor args are required, properties are optional. This is by design. I > think there are white papers on the subject of ctor vs. property > injection and the connotation of each. > > On Jul 9, 5:49 pm, Mauricio Scheffer <[email protected]> > wrote: > > > > > I just tested this on 2.0, it works for optional parameters but not > > for constructor (mandatory) parameters, so it looks like a bug to me. > > Gonna check trunk to confirm. > > > On Jul 9, 12:41 pm, Michael Yeaney <[email protected]> wrote: > > > > Hello all... > > > > I'm using Castle 1.0.3.433 and have question regarding the > > > Resolve<T>(IDictionary args) method. It seems that if the XML > > > configuration > > > file has values specified for constructor arguments, the IDictionary will > > > NOT override these values. This is not what I expected. I was hoping > > > that > > > I could specify defaults in the config file, but override them at runtime. > > > > Any thoughts? > > > > TIA, > > > Michael --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
