here's my bias 2 bits on rule configuration. in the past when I've built rule servers, the configuration included the following modules and components in the deployment description.

1. rulesets - a list of rulesets
2. initial facts - facts needed to run the rules
3. modules - like functions
4. models - domain object model
5. number of engine instances - for creating a pool
6. min pool number - initial number of engines
7. max pool number - max number of engines
8. name - name for the configuration if there are multiple

I imagine for the solver you're NOT talking about a general purpose deployment configuration, but thought i'd provide some food for thought.


peter

On 1/23/07, Geoffrey De Smet <ge0ffrey.spam@gmail.com> wrote:
For the solver I 'd like to externalize the configuration into an xml(?)
  file.
something like

<localsearch decisionMode="OPTIMAL">
    <finish steps="500"/>
    <ruleBase location="/org/foo/bar/drools.drl"/>
</localsearch>

This is a bit inspired by how ehcache is configured, clean and easy,
without any class implementation details: the way users like it.


I 've been thinking on doing this with XStream, but that's not versatile
enough to make user friendly configuration files. Although Xstream works
out great to serialize solutions to and from xml files.

Next I was thinking about is JDom or Xom, but that's yet another
dependency. What would you guys recommend?


--
With kind regards,
Geoffrey De Smet

_______________________________________________
rules-dev mailing list
rules-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-dev