https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/INFRAUTILS-63 infrautils <p>infrautils.inject</p> <ol> <li>Scan for @Service on @Singleton to find interface to bind to</li> <li>interface WiringProvider extends Provider&lt;Map&lt;Type, Object&gt;&gt;</li> <li>WiringReflectiveWiringProvider which looks for getters on *Wiring</li> </ol> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java"><span class="code-keyword">class </span>ModuleBuilder { Module build(); <span class="code-comment">// ignore duplicates, auto inject ClasspathScanner </span> addModule(<span class="code-object">Class</span>&lt;Module&gt; moduleClass); addPackage(<span class="code-object">String</span> packageName);</pre> </div></div> INFRAUTILS-63

Guice Inject utility ideas

New Feature Medium Resolved Won't Do Michael Vorburger Michael Vorburger Wed, 30 Jan 2019 14:59:47 +0000 Mon, 4 Feb 2019 13:56:22 +0000 Mon, 4 Feb 2019 13:56:22 +0000 0 1 <p>It occurred to me, with a few days distance, that any such "magic" like what I imagined above, would make error tracking for Guice DI much more difficult than with today's still (once you are used to them) clear errors... Guice points out which Module what binding is from - but it could not do that anymore if we did above, so I think this is actually NOT a good idea - so closing this.</p> Relates CONTROLLER-1831 Development Rank 0|i03mg7: