Alin Dreghiciu wrote: > Sounds good to me. @Optional indeed sounds better then @Nullable. Tool > support is good off course but unit tests should be there anyhow and > catch eventual problems, isn't it. > I would go for @Optional.
We already have an @Optional annotation, but the good news is that it isn't really used, so repurposing it for this would be no problem at all. /Rickard _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
