Seems like that ought to apply to @avalon tags. The various descriptors ought to be merged for each of the classes in the inheritance tree.
I've always been confused about what would happen with regard to the meta tags if I decided to subclass a component.
One prime example of that is in porting the Cornerstone components to using the @avalon tags. The socket manager blocks has just such an abstract base class with derived components for plain socket servers and TLS socket servers. Would be curious how those components would re-tooled with @avalon tags without redesigning the classes themselves.
- timothy
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
