source: http://isagoksu.com/2009/development/java/creating-custom-annotations-and-making-use-of-them/
Okay, here is another topic that I couldn’t find much information in the Internet :) So I guess I’m gonna cover it quickly.
How to Create a Custom Annotations?
There are a lot of documentation about this part in the Internet. All you have to do is basically creating an annotation class like below:
And that’s it. Now it’s ready to use! Now you can put copyright information to your classes :) Since we didn’t define any @Target, you can use this annotation anywhere in your classes by default. If you want your annotation to be only available for class-wise or method-wise, you should define @Target annotation. Here is a little table of what options are available:
- @Target(ElementType.PACKAGE), package header
- @Target(ElementType.TYPE), class header
- @Target(ElementType.CONSTRUCTOR), constructor header
- @Target(ElementType.METHOD), method header
- @Target(ElementType.FIELD), for class fields only
- @Target(ElementType.PARAMATER), for method parameters only
- @Target(ElementType.LOCAL_VARIABLE), for local variables only
If you want your annotation to be available in more than one place, just use array syntax as in:
One thing you may already notice is annotations are interfaces, so you don’t implement anything in them.
How to Make Use of Your Custom Annotations?
Up to here, you can find lots of examples. Okaaay, now let’s do something useful :) For instance, let’s re-implement JUnit’s @Test annotation. As you guys already know,@Test annotation is a marker annotation. Basically it marks the method as test method. If you’re expecting any exceptions, you would set expect attribute in the annotation. You can try anything here, I’m just using this example since everyone knows how @Test annotation works.
First let’s define our annotation:
You might notice that I used @Retention. This annotation marks our annotation to be retained by JVM at runtime. This will allow us to use Java reflections later on.
Now we need to write our annotation parser class. This class will parse our annotation and trigger some other invocations related to what we want. Keep in mind that if you have more than one custom annotation, then it’s also wise to have separate parsers for each annotation you define. So I’ll create one for this! The basic idea behind the annotation parser is using Java reflections to access the annotation information/attributes etc. So here is an example parser for our @Test annotation:
That’s all you need. You parser is ready to use too. But wait a minute, we didn’t implement anything about the annotation attributes. This part is a bit tricky. Because you cannot directly access those attributes from the object graph. Luckily invocation helps us here. You can only access these attributes by invoking them. Sometimes you might need to cast the class to the annotation type too. I’m sure you’ll figure out when you see it:) Anyways here is a bit more logic to take our expected attribute into account:
Now everything is ready to use. Below example demonstrates how you use Parser with your test classes:
Yeah, I hope you enjoyed. Don’t hesitate to put some comments down if you’ve a better approach? Thanks! Here is the full parser class implementation:
Edit: Also after receiving some emails, I guess I should add a full working example :) So here is one. Just copy paste and run the show :)
댓글
댓글 쓰기