1 Java Programming: Doing your own annotations {anchor:Java Programming: Doing your own annotations} With the release of Java 5 a new feature called annotation showed up. Probably you have already seen it, or even used it. Basically annotations are metadata you insert in you classes and can be identified by the keyword __@annotation_name__. \\ Maybe you've already used java built-in annotations, such as __@Deprecated__ or __@Override__, but I'm not gonna talk about the existing annotations, I'm writing about how you can create your custom annotation, so let's start. First of all you have to ask yourself the following: 1. What will be the name of the annotation 1. What arguments will it receive Let's now build 2 annotations, one without any arguments - which is commonly called a marker - and one with 2 arguments. In the first case, programming a marker is as simple as: {code} package net.pabrantes.annotations public @interface MyMarker { } {code} Now after compiling it, you can use the new annotation referring to it as __@MyMarker__. Although, this being a marker we want to specify that it should be discarded by the compiler. That can be done setting up the {link:__retention policy__|url=http://download.java.net/jdk6/docs/api/java/lang/annotation/Retention.html|newWindow=true}. You can set the retention policy to retain the annotation only at the source code by doing the following: {code} package net.pabrantes.annotations @Retention(java.lang.annotation.RetentionPolicy.SOURCE) public @interface MyMarker { } {code} Yes, you just have annotated an annotation! Below you can find a description of each value that the retention policy can take. {table} Policy Name | Policy | SOURCE | Annotation is discarded at compile time | CLASS | Annotation goes into class file but the virtual machine does not retain it | RUNTIME | Annotation goes into class file and and retained by virtual machine. They can then be read by reflection API. | {table} You can also annotate an annotation to tell what elements can be annotated, but we will get there later. First, let's build our annotation with two parameters.\\ Code follows: {code} package net.pabrantes.annotations public @interface MyAnnotation { public enum SomeSortOfEnum { VALUE1, VALUE2 }; public String parameter1(); public SomeSortOfEnum parameter2(); } {code} So now you can annotate your code doing the following: {code} @MyAnnotation(parameter1="a string", parameter2=SomeSortOfEnum.VALUE1 } public void method(...) { ... } {code} But imagine that you want to allow the programmers to only specify parameter2, and that if no parameter1 is specified it defaults to __"My String"__. To do that we have to adjust a bit our annotation source code. {code} package net.pabrantes.annotations public @interface MyAnnotation { public enum SomeSortOfEnum { VALUE1, VALUE2 }; public String parameter1() default "My String" ; public SomeSortOfEnum parameter2(); } {code} Finally imagine that you want to allow the use of this annotation only in methods of a class and the constructors. To do this you have to set the target elements, and that is done using another annotation, called __@Target__.\\ Here is how it can be done: {code} package net.pabrantes.annotations import static java.lang.annotation.ElementType.METHOD; import static java.lang.annotation.ElementType.CONSTRUCTOR; @Target({METHOD,CONSTRUCTOR}) public @interface MyAnnotation { public enum SomeSortOfEnum { VALUE1, VALUE2 }; public String parameter1() default "My String" ; public SomeSortOfEnum parameter2(); } {code} Below you can find a table with all the values of {link:ElementType|url=http://download.java.net/jdk6/docs/api/java/lang/annotation/ElementType.html|newWindow=true}. {table} Type | Description | ANNOTATION_TYPE | Declares that the annotation is used to annotate other annotations | CONSTRUCTOR | Declares that the annotation is used to annotate constructors | METHOD | Declares that the annotation is used to annotate methods in the class, constructors are not included in this type | FIELD | Declares that the annotation is used to annotate field declarations | LOCAL_VARIABLE | Declares that the annotation is used to annotate a local variable| PARAMETER | Declares that the annotation is used to annotate a parameter | PACKAGE | Declares that the annotation is used to annotate a package| TYPE | Declares that the annotation is used to annotate a Class, interface or Enum| {table} After reading this post I think it's safe to say that you have the necessary knowledge to write your own annotations, although, don't start going nuts writing custom annotations for everything. \\ Before writing your new custom annotation ask yourself if it's really needed, otherwise you have the risk of excess of annotations in your code, which as you can imagine is not good at all. 2006-07-04 00:56:10.549 2006-07-04 00:53:51.594 Ok this is in no shape way or form related to the cool ass article about annotations (which btw now I am able to use myself :) ) but with the fact that the site (or actually the code blocks) looks bad in Firefox on OS X (10.4.7). The code sticks together (words run into each other or overlap each other) please advise :P :) 2006-07-06 18:34:51.636 2006-07-06 18:34:51.456 Well I'm glad you liked the post and taught you something... Finally I wrote something useful! ~~laugh~~ Anyway regarding the code blocks I find that really strange, since I'm also using Firefox (1.5.0.4) and OS X (10.4.7) and the code looks excellent. Maybe it's the font you are using... Don't really know, since I'm not that UI guy... But sounds like a CSS problem. My default font is Times size 16. If you haven't that please retry...Also if it's not, it's better to report such behaviour to the snipsnap developers: * Matthias L. Jugel (matthias.jugel -at- first.fraunhofer.de) * Stephan J. Schmidt (stephan.schmidt -at- first.fraunhofer.de) Send them a screenshot along with your font information. And it would rock if you spotted the problem in the CSS. 2006-07-06 20:42:11.436 2006-07-06 20:42:11.355