On Wed, 10 Nov 2004 10:05:29 +0100, Knut Wannheden <[EMAIL PROTECTED]> wrote: > > 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? >
Expanding on this last idea... A registry which maps resource path patterns to module descriptor providers would of course mean that the providers are bound to resources -- i.e. module descriptors must be loaded from resources. But doesn't the <sub-module> element already impose this restriction? OTOH this may be a reasonable restriction. What do you think? As a consequence the RegistryBuilder and ModuleDescriptorProvider interfaces would change yet another time! ;-) --knut --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
