On Sat, 12 Jan 2002 01:56, Paulo Gaspar wrote: > Basically, there is one (or more) XML configuration file that > configures all Roles and Types which specifies their names, > interfaces (role), class factories (type), etc. > > Then there is one (or more) XML files that configure the sitemap. > > Note: A "type" is a specific implementation of a "role" and a role > is an interface just as in Avalon.
Thats the terminology I tend to use aswell ;) > I sent you the FACTORY code. The component has NO configuration > points and in this case is not even dependent on the framework. Actually it has many configuration points and is not dependent on framework ;) Rather than expose one public method to configure service you expose N different setters and each of these setters is another hinge point. > > However, that is a matter of preference. > > Actually, from what you say we have the same preferences. I just > have to do a better job of explaining my ideas. No I understand them and I agree that they tend to work better when you are using Avalon to just create the components rather than manage them. As you said I tend to use almost the same architecture in Myrmidon. I started out using ComponentSelector/ECM and friends but found that it became too complicated to manage and too highly coupled. However if I was writing a webserver/mailserver/imserver/whateverserver I think I would still use Avalons current mechanisms. -- Cheers, Pete -------------------------------- These aren't the droids you're looking for. Move along. -------------------------------- -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
