Hello Rafal,
Not really what I meant. You wrote "Since my components are generally not
dependent on particular IoC framework, I could use castle instead, but it's
a lot of work which I dont have time to do now."
Since your components aren't dependent on a particular IoC framework, they
won't have to be changed. Left to change which can take time is possibly
services provided by the IoC framework, such as Spring.Net's automatic web
service-feature.
Assuming you're not too dependent on these custom services, I was merely
tipping you off, that if you wish to recode your IoC config with Windsor
instead, then it would be a lot quicker to use a facility, and in there,
register all your components with the fluent API, which is much much quicker
than the XML Spring.Net uses, or the XML you can use for Windsor.
A facility is a plugin, so in your config:
<facilities>
<facility id="fac" type="Asm.MyFacility, Asm" />
</facilities>
And then in
Class MyFacility : AbstractFacility:
public override void Init()
{
Kernel.Register(Component.For<T>.ImplementedBy<T2>())
}
For all your components, which of course allows you the use of
CTRL+ALT+SPACE when writing the type name for finding all these references
very quickly if you're using something like ReSharper. I postulated this
might take around 20 minutes to do if you have a big project, and as such,
it might be solving your problems.
Regards,
Henrik
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of rg
Sent: den 8 april 2009 07:22
To: Rhino Tools Dev
Subject: [rhino-tools-dev] Re: Rhino service bus with Spring.net container
Henrik, what do you mean by 'use facilities' - what facilities? And should I
code anything at all? I thought wiring up everything is a job of the
container and I should only provide the config?
Regards
Rafal
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Rhino Tools Dev" 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/rhino-tools-dev?hl=en
-~----------~----~----~----~------~----~------~--~---
