Hey, I just committed support for constraints in the new model. No support for compound constraints yet, but that should be reasonably easy to add with the new model I think.
Also applied patches from Michael which hides a number of model classes as implementation details. This pattern can probably be applied even more I would think. Cleaned up some things which were not really used (like ParametersModel, which is replaced by MethodConstraintsModel and InjectedParametersModel respectively), and renamed BindingContext to Resolution. In a sense I think the previous pattern with Model/Resolution/Binding/Context was correct, it just was not manifested correctly. Instead of having each of these be separate classes it should be as it is now, where the Model is a class, the Binding is a method with the Resolution as parameter, and then Context are the business methods exposed by the result. Makes much more sense, and the code is muuuuuuch easier to read/code. As it is now the Energy4Java runtime class has no value as a holder of builders/factories, and it will probably be demoted to just be the API/SPI/runtime bridge (e.g. exposing runtime information in the API where necessary). I'm moving on with objects now (i.e. plain classes), since I don't want to wait too long before getting those into the overall model. Looking good overall. /Rickard _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
