Acording to this post:
http://groups.google.com/group/castle-project-devel/browse_thread/thread/296dd82d5decd226/e5106c9ef7671710?hl=en&lnk=gst&q=MicroKernel+additionalArgs+behavior+definition#e5106c9ef7671710
This should work:
var sender = container.Resolve<Calculator>(new {parameterNameOfIWriter =
value} );
On Wed, Feb 11, 2009 at 2:26 PM, Daniel Hölbling <[email protected]>wrote:
> Hello,
>
> I am currently facing a interesting problem with my Windsor object
> creation.
>
> I have a service that calculates something and then calls a Writer service
> to save this calculation.
>
> So I have Calculator depend on IWriter through it's ctor.
>
> This all works.
> But now I have a special case where I need get a Calculator that is hooked
> up to a decorated IWriter that has one of it's dependencies supplied at
> runtime.
> In more concrete terms I try to apply a filter through the decorator, so I
> need to resolve a Calculator object that depends on a Filtered IWriter (with
> a runtime-supplied filter argument) and the Filter-Decorator then passes the
> call on to the "real" IWriter that then goes into the DB.
>
> Now, container.Resolve<Calculator>(arguments) would work if I need to pass
> an argument to the calculator.
> But how do I supply the arguments to the subsequent IWriter lookup?
>
> Is there some way to pass arguments to subsequent resolves?
>
> The obvious fallback would be to simply construct that object by hand. But
> that's not really ideal imo.
>
> Any help would be greatly appreciated.
> greetings Daniel Hoelbling
>
> (PS: Sorry if this went to the list twice, I may have forgotten to change
> my from field to the one registered at google)
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
