<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Dexopt on Brave New Geek</title><link>https://bravenewgeek.com/tag/dexopt/</link><description>Recent content in Dexopt on Brave New Geek</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 25 Jan 2019 10:52:38 -0600</lastBuildDate><atom:link href="https://bravenewgeek.com/tag/dexopt/index.xml" rel="self" type="application/rss+xml"/><item><title>Implementing Spring-like Classpath Scanning in Android</title><link>https://bravenewgeek.com/implementing-spring-like-classpath-scanning-in-android/</link><pubDate>Sat, 05 Jan 2013 02:53:36 -0600</pubDate><guid>https://bravenewgeek.com/implementing-spring-like-classpath-scanning-in-android/</guid><description>&lt;p&gt;One of the things that Spring 2.5 introduced back in 2007 was component scanning, a feature which removed the need for XML bean configuration and instead allowed developers to declare their beans using Java annotations. Rather than this:&lt;/p&gt;
&lt;script src="https://gist.github.com/tylertreat/7688bafe73aa1eaeaa24.js"&gt;&lt;/script&gt;
&lt;p&gt;We can do this:&lt;/p&gt;
&lt;script src="https://gist.github.com/tylertreat/937b3e36d6ecdcbc7c3b.js"&gt;&lt;/script&gt;
&lt;p&gt;It’s a pretty simple idea since Java makes it very easy to introspectively check a class’s annotations at runtime through its reflection API. Spring’s component scan feature also allows you to specify the base package(s) to scan for beans.&lt;/p&gt;</description></item></channel></rss>