The problem is I like the ideas behind RSB very much and with the
addition of Rhino queues I'm definitely
convinced that it matches my needs better than any other message bus
for .Net. Unfortunately, I like
the spring container too and have already used it as a base of my
project. 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. And what if some other guy writes
another great component that I'd
like to use, but it will require different IoC?
Rafal


On Apr 5, 10:45 pm, Mike Nichols <[email protected]> wrote:
> @Rafal
> If you are in a position not to work with Castle you may want to take a look
> at NServiceBus. It might be more Spring friendly for you.
>
> On Sun, Apr 5, 2009 at 11:08 AM, Ayende Rahien <[email protected]> wrote:
> > I am serious. See recent discussion in the mailing list.RSB is composed of
> > a LOT of very small components that are being brought together by the
> > container. As such, trying to use something is CSL will not work.
> > Moreover, I have exactly zero interest in trying to maintaing the
> > registration lists for all the containers out there, especially since this
> > is something tat changes every time we make a significant modification to
> > RSB.
>
> > On Sun, Apr 5, 2009 at 10:33 AM, nightwatch77 
> > <[email protected]>wrote:
>
> >> Thanks Ayende, I mean are you serious, or it's just an irony?
> >> Now this is a big problem for me if adopting RSB requires me to change
> >> the IOC container from Spring to Castle Windsor.. Mainly because I
> >> don't know castle windsor at all and it's not documented very well.
> >> Isn't this dependency on IOC container going a bit too far?\
> >> 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
-~----------~----~----~----~------~----~------~--~---

Reply via email to