<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Annotation on ilikeorangutans</title><link>https://kuelzer.ca/tags/annotation/</link><description>Recent content in Annotation on ilikeorangutans</description><generator>Hugo</generator><language>en</language><copyright>© 2026 Jakob Külzer</copyright><lastBuildDate>Sun, 12 Apr 2026 14:27:24 -0400</lastBuildDate><atom:link href="https://kuelzer.ca/tags/annotation/index.xml" rel="self" type="application/rss+xml"/><item><title>JSR-269 Annotation Processing</title><link>https://kuelzer.ca/posts/2013/08/13/jsr-269-annotation-processing/</link><pubDate>Tue, 13 Aug 2013 13:59:40 -0400</pubDate><guid>https://kuelzer.ca/posts/2013/08/13/jsr-269-annotation-processing/</guid><description>&lt;p&gt;I&amp;rsquo;ve been contemplating compile time bytecode manipulation for the &lt;a href="http://www.objectmapper.org/"&gt;Object Mapper Framework&lt;/a&gt; for a while now. Compile time instrumentation of classes seems to be a better approach and does away a whole lot of class loading issues, especially in OSGI environments. In any case, I remembered &lt;a href="http://projectlombok.org/"&gt;Project Lombok&lt;/a&gt; and reading about &lt;a href="http://jcp.org/en/jsr/detail?id=269"&gt;JSR-269&lt;/a&gt;, which was introduced with Java 1.6. It&amp;rsquo;s an API that allows you to plug custom annotation processors into javac.&lt;/p&gt;
&lt;p&gt;After experimenting and reading a bit, here is my reading list:&lt;/p&gt;</description></item></channel></rss>