> > I'm kind of surprised that this works how it does. It seems like > > there's no difference between a component that implements > IStartable > > and a component that initiates its work via a constructor > > I'm sorry but there's a big semantic difference. Constructors > should initialize the object to a prepared state, and stop > there. An initializable component acts almost like a windows > service as it can be started and stopped.
It's funny you should mention a Windows Service, because that's exactly what I'm working with. I wouldn't expect a Windows Service to start before its dependencies were satisfied. What I'm realizing here is that I managed to miss a pretty important part of the documentation on the site and I totally overlooked that you can actually inject properties. For some reason I was under the misconception that it was constructor or nothing. Windsor makes a lot more sense to me now. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ CastleProject-users mailing list CastleProject-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/castleproject-users
