This is something I'm interested in, though it represents a bit of change in how service models work.
If we pursue the bootstrap option, then service models would go into hivemodule-bootstrap.xml, not hivemodule.xml. Bootstrap: we build a simplified registry and use *that* to parse and construct the real registry. It helps to break down some chicken-and-the-egg problems with exactly the types of things we're describing here. -- Howard M. Lewis Ship Independent J2EE / Open-Source Java Consultant Creator, Tapestry: Java Web Components http://howardlewisship.com > -----Original Message----- > From: Geoff Longman [mailto:[EMAIL PROTECTED] > Sent: Thursday, March 11, 2004 10:18 AM > To: Jakarta Commons Developers List > Subject: [Hivemind] Adding service models > > > Looking at the code I see that service models in Hivemind is > hardcoded in > that an Enum lists the types allowed. > > Just want to throw this idea over the fence.. > > What if , in addition to the default service models, there was a > configuration point for modules to contribute thier own > service models? > > > Geoff > > Geoffrey Longman > Intelligent Works Inc. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
