Hi all, I've been thinking quite a bit along these lines lately. Especially since there have been many other questions and comments which seem to be pushing in this direction. What I believe HiveMind needs is a terse API to construct a HiveMind registry.
I know we already have an API for defining the constituents of the registry: RegistryBuilder along with ModuleDescriptorProvider and all the o.a.h.parse.*Descriptor classes. IMO this API has a lot of concepts which are specific to HiveMind's XML syntax: schemas, schema rules, conditional contributions (and conditional expressions), and possibly more. The API I had in mind would define interfaces for the central concepts Module, ServicePoint, Implementation, Interceptor, ConfigurationPoint, and Contribution. The XML parsing with the *Descriptor classes would then be using this API. What do you think about this? Should I try to document a change proposal on the Wiki? --knut On 5/6/05, Howard Lewis Ship <[EMAIL PROTECTED]> wrote: > So I had an idea for an alternate way of getting objects instantiated, > that borrows from the Ruby approach. This is an addition to the > traditional HiveMind (XML) approach. > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
