MATSim Code

extract classes in their own files

SelectExpBeta was forgotten...

throw exception if unknown tag

this would be the job of a dtd...

RunUtils provide two methods to load strategy

(1) "legacy" one (from weights config group)
(2) "modular" one (from group replanning config group)

(1) should go as soon as possible

non-flat strategy config group

analogous of ReflectiveConfigGroup for non-flat config groups

uglyly done: copy-paste of ReflectiveModule, changing te "extends"
statement from Module to NonFlatModule.

an analogous of PlanStrategyRegister

rename

probably better to keep this approach under the elbow while implementing
the new config group and all: allows not to break config files of the
current runs.

move factory methods to individual classes

rename GroupPlanStrategyFactory to GroupPlanStrategyFactoryRegistry and move module creating methods in a utils class

idea: go toward something similar to vanilla matsim's
PlanStrategyRegistry