Just had an interesting thought. What if bootstrapping the Registry was a two step process?
How about if we first built a Registry based on META-INF/hivemind-bootstrap.xml files. The services and configurations for this Registry exist to set up the main bootstrap. For example, there would be services and configuration points to guide the module location and parsing, and to (for example) define the available translators and (potentially) the available XML rules ... maybe even the different service models. We could then reach into the bootstrap Registry for a service that would create the runtime Registry. The Bootstrap registry is then discarded. -- Howard M. Lewis Ship Creator, Tapestry: Java Web Components http://jakarta.apache.org/tapestry http://jakarta.apache.org/commons/sandbox/hivemind/ http://javatapestry.blogspot.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
