----- Original Message ----- From: "Stephen McConnell" <[EMAIL PROTECTED]>
> org.apache.avalon.composition.model.impl.Scanner (in the > merlin/composition/impl package) you will see an example of the appraoch > used within the Merlin container (basically for all entries in the > classpath, scan each entry for component definitions). That's very simple indeed. The .roles file in Fortress will be overrided by meta, I wonder about the .xconf files... I saw .xprofile files in merlin, seems nice. As curiosity: is this the only way to configure components? Are we planning a wonderfull world where people could deploy their services on fortress or merlin without bothering about their differences? If so, the Avalon meta is the first step - from my point of view - and more things, like Merlin scanner, should go up to a common-shared project to be used by merlin and fortress and by anyone who feels like want to. I still believing in a container spec in a neutral language/plataform fashion with basics rules that container implementors must follow and suggestions of implementation. Regards, hammett --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
