[rules-dev] externalize solver configuration - which technology?

[Michael Neale]

it dependency lightness is important (it is !) just the plain old Dom or
Sax?

Take a look at the XML parser for the DRLXML format in Drools 3 - its
reasonably flexible (hand coded to some extent) but just uses standard
stuff.

On 1/24/07, Geoffrey De Smet <ge0ffrey.spam at 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 at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/rules-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/rules-dev/attachments/20070124/c40eac19/attachment.html