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

Michael told me on irc that XStream might also be a good idea. Since I 'd like the configuration as a separate domain object model, I tryed it that way and it looks ok: <LocalSearchSolver> <randomSeed>5</randomSeed> <finish class="StepCountFinish"> <maximumStepCount>50</maximumStepCount> </finish> </LocalSearchSolver> What do you think of such kind of local search solver configuration? Here are the classes that do it, they follow the builder pattern: @XStreamAlias("LocalSearchSolver") public class LocalSearchSolverConfig { private long randomSeed = 0; @XStreamAlias("finish") private FinishConfig finishConfig; public LocalSearchSolver build() ... } @XStreamAlias("StepCountFinish") public class StepCountFinishConfig implements FinishConfig { private int maximumStepCount = 100; public Finish build() ... } which looks a lot easier than fiddling around with sax or DOM? Xsd might be a problem - but maybe some day XStream can use the javadocs to generate an xsd? If not, it shouldn't be to hard to replace the config package with a sax or dom based configuration - or just manually write an xsd. With kind regards, Geoffrey De Smet Mark Proctor wrote: