it dependency lightness is important (it is !) just the plain old Dom or Sax?<br><br>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.
<br><br><div><span class="gmail_quote">On 1/24/07, <b class="gmail_sendername">Geoffrey De Smet</b> <<a href="mailto:ge0ffrey.spam@gmail.com">ge0ffrey.spam@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
For the solver I 'd like to externalize the configuration into an xml(?)<br> file.<br>something like<br><br><localsearch decisionMode="OPTIMAL"><br> <finish steps="500"/><br> <ruleBase location="/org/foo/bar/drools.drl"/>
<br></localsearch><br><br>This is a bit inspired by how ehcache is configured, clean and easy,<br>without any class implementation details: the way users like it.<br><br><br>I 've been thinking on doing this with XStream, but that's not versatile
<br>enough to make user friendly configuration files. Although Xstream works<br>out great to serialize solutions to and from xml files.<br><br>Next I was thinking about is JDom or Xom, but that's yet another<br>dependency. What would you guys recommend?
<br><br><br>--<br>With kind regards,<br>Geoffrey De Smet<br><br>_______________________________________________<br>rules-dev mailing list<br><a href="mailto:rules-dev@lists.jboss.org">rules-dev@lists.jboss.org</a><br><a href="https://lists.jboss.org/mailman/listinfo/rules-dev">
https://lists.jboss.org/mailman/listinfo/rules-dev</a><br></blockquote></div><br>