Hi again, 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 have now committed the required framework changes to enable reuse for the Groovy support and am more or less done with the Groovy support. What remains is the documentation part. As the Groovy support doesn't yield any new services or configurations I'm not quite sure where we should document it. I was thinking of creating a new page under the main "Tutorials and Information" item called "Building a Custom Registry" or something like that. There we could document how to use the RegistryBuilder in a non-standard fashion. E.g. loading XML descriptors from a non-standard location, using a different ErrorHandler (e.g. StrictErrorHandler), or loading non-XML module descriptors. Here we could include an example of how to load a Groovy script defining a module into the Registry. What do you think? --knut --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
