On Sat, Apr 12, 2008 at 4:50 PM, Rickard Öberg <[EMAIL PROTECTED]> wrote:

>  Two things I want to do next are:
>  * Allow the @Constraints declaration to be on the actual annotation
>  interface rather than in the Composite type declaration. This will make
>  it sooo much easier to use

So this is what we talked about before, i.e. if there are constraint
annotations on methods and properties, they can be forced to be
evaluated, and not just "forgotten" in the Composite declaration's
@Constraints() ?? But that we can still override...

If so, +10

>  * Allow compound Constraints, such as:
>
>  @ConstraintDeclaration
>  @NotNull @Matches("\d{n,}")
>  @interface ZipCode {}

Excellent idea!


Cheers
Niclas

_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev

Reply via email to