Error setting a default null value for an annotation’s field

by

I don’t know why, but the JLS is very clear:

 Discussion

 Note that null is not a legal element value for any element type.

And the definition of a default element is:

     DefaultValue:
         default ElementValue

Unfortunately I keep finding that the new language features (Enums and now Annotations) have very unhelpful compiler error messages when you don’t meet the language spec.

EDIT: A little googleing found the following in the JSR-308, where they argue for allowing nulls in this situation:

We note some possible objections to the proposal.

The proposal doesn’t make anything possible that was not possible before.

The programmer-defined special value provides better documentation than null, which might mean “none”, “uninitialized”, null itself, etc.

The proposal is more error-prone. It’s much easier to forget checking against null than to forget checking for an explicit value.

The proposal may make the standard idiom more verbose. Currently only the users of an annotation need to check for its special values. With the proposal, many tools that process annotations will have to check whether a field’s value is null lest they throw a null pointer exception.

I think only the last two points are relevant to “why not do it in the first place.” The last point certainly brings up a good point – an annotation processor never has to be concerned that they will get a null on an annotation value. I tend to see that as more the job of annotation processors and other such framework code to have to do that kind of check to make the developers code clearer rather than the other way around, but it would certainly make it hard to justify changing it.

More Related Contents:

  1. Spring: @Component versus @Bean
  2. Only using @JsonIgnore during serialization, but not deserialization
  3. Xml configuration versus Annotation based configuration [closed]
  4. Is it possible to read the value of a annotation in java?
  5. Java Annotations values provided in dynamic manner
  6. What is the use of marker interfaces in Java?
  7. How to annotate MYSQL autoincrement field with JPA annotations
  8. Should we @Override an interface’s method implementation?
  9. Which types can be used for Java annotation members?
  10. Adding Java Annotations at Runtime
  11. What is the purpose of @NamedArg annotation in javaFX 8?
  12. How do different retention policies affect my annotations?
  13. JFreechart series tool tip above shape annotation
  14. Why doesn’t a missing annotation cause a ClassNotFoundException at runtime?
  15. Hibernate : How override an attribute from mapped super class
  16. Retrieve Java Annotation Attribute
  17. Annotations from javax.validation.constraints not working
  18. How to scan multiple paths using the @ComponentScan annotation?
  19. @OneToMany and composite primary keys?
  20. Why is default required for a switch on an enum?
  21. Java String validation using enum values and annotation
  22. Annotating the functional interface of a Lambda Expression
  23. Spring @ContextConfiguration how to put the right location for the xml
  24. Meaning of Android Studio error: Not annotated parameter overrides @NonNull parameter
  25. Which @NonNull Java annotation to use [duplicate]
  26. BeanNotOfRequiredTypeException due to autowired fields
  27. enable Annotation Processors option in Android Studio 2.2
  28. Hibernate: Data Object with a dynamic table name by Annotations
  29. How to map one class to different tables using hibernate/jpa annotations
  30. Can the annotation variables be determined at runtime?

Leave a Comment