I tried to solve the problem that Niclas stated earlier, i.e. the
ConstraintDeclarationModel stuff.
The question that arises here is that this is a three level hierarchy
modelling the annotations
on a property:
n times @ConstraintDeclaration{
at one @Constraints
m times ConstraintImplementations in values
}
this is modelled by
ConstraintsModel
containing the n times @ConstraintsDecl-Annotations
and n times ConstraintsDeclModel
which contains the annotationType of the @ConstraintsDecl
and m times ConstraintModel which contains the
ConstraintImplementation, the annotationType of @ConstraintsDecl
1. is this 3 level hierarchy necessary ?
2. is it allowed to store Annotations in the Model, if yes why is so
much effort done to extract all the information from the Annotations
upfront, if no why is a List<Annotation> stored in the ConstraintsModel
3. why is the base class Annotation used at almost every occurence and
not the concrete Annotation type (e.g. List<ConstraintsDecl> instead of
List<Annotation> in ConstraintsModel
4. Why don't the models refer to each other, this would ease the
navigation between the models ( not just the constraints here but also
the Methods, Fields, Constructors and their ParameterModels and
PropertyModels and the other Models that exist there).
So long,
Michael
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
