There's a limit to how much of HiveMind you can define in HiveMind
itself.
My
long term concept is to have one set of descriptors and configurations that are
used to bootstrap the environment. Those are then used to read the actual
HiveMind MDDs. You would put things like service models, translators and
rules into the bootstrap descriptors, then use them in the main descriptor ...
most applications would not know of or use the bootstrap
descriptor.
--
Howard M. Lewis Ship
Independent J2EE / Open-Source
Java Consultant
Creator, Jakarta Tapestry
Creator, Jakarta HiveMind
http://howardlewisship.com
-----Original Message-----
From: Steve Gibson [mailto:[EMAIL PROTECTED]
Sent: Friday, June 11, 2004 11:13 AM
To: [email protected]
Subject: Rules, properties and Rule extension pointAnother multi-part email (sorry, can't help it)1. Specifiying properties / attributes for RulesI am writing a custom rule that I want to pass 2 parameters to. Built-in rules already do this, but I can see how the SchemaProcessor, etc know what to do.I am going to just put the accessors/mutators into the class and see if through the magic of Java Beans that it works, but if this doesn't work, what is the right way to do this...or is there (see part 2).2. Would it be useful and feasible to have an extenstion point for Rules like there is for Translators? It did seem odd to me at first that there wasn't. I realise the list of contributors at this point is low, but I think that, barring complexities within the parsing system, should be reapplying a common pattern, increase consistency, should not affect simplicity (as you don't "see" an extension point until you want to use it) and should also make it easier to contribute rules.Steve GibsonSoftware EngineerCOWWW Software
