On Thu, 4 Nov 2004 10:46:31 +0100, Knut Wannheden <[EMAIL PROTECTED]> wrote: > > 4. Support for Groovy module descriptors. I have implemented a > GroovyModuleDescriptorProvider which I thought we could add to > hivemind-lib. This would although add a dependency on a groovy.jar. > Further the implementation requires that the DescriptorParser can be > used as a normal XML ContentHandler. This can be accomplished by > adding alternative initialize() and a getModuleDescriptor() methods. > But splitting it into two classes somehow would probably be cleaner. >
I was just about to finish up the Groovy support when I came to think of a problem. What should the GroovyModuleDescriptorProvider do (or in fact any ModuleDescriptorProvider) with encountered <sub-module> elements? Try to parse the referenced submodule resource as a resource of the same type (e.g. Groovy script) or as a default XML descriptor? I suppose this could just be a limitation for now, but the clean solution would probably be to require the providers to be registered with some kind of registry, where they are associated with resource path patterns (filename extensions in the simplest case). Thoughts? --knut --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
