> I suggest you just say "Supports Avalon Components (Framework 4.1.x)" > on your website, and be done with it. Just as I can say "My program > runs on Linux" without getting into a trademark debate with Mr. > Torvalds, because, well, *it does*. It's just a feature list.
Agreed. But anyway even the compatibility between avalon's containers is on board... Being able to provide: 1. a neutral container spec and/or 2. a set of test cases Will stop this from hunt us till the end of ours days... Meanwhile I would like to know -> ***WHY*** Cocoon depends so much on Selectors. -> Fortress lets a components lookup for another components that its not a dependecy of itself. Well. Is this behavior under avalon framework *spec*? Will then have a rigid container - ie Merlin - and a *friendly* one - Fortress/ECM. Would be better to a have one and only one position about this. -- hammett --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
