Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>I found the following to be of use:</p> <ol> <li>split your Spring configurations into multiple standalone configurations, and use Spring's import facility to import configuration dependencies (see <a href="http://static.springframework.org/spring/docs/2.0.8/reference/beans.html" rel="nofollow noreferrer">here</a>, section 3.2.2.1). That way you have a set of configurations that you can combine or disassemble as required, and they are all self-dependent (all the dependencies will be explicit and referenced)</li> <li>Use an IDE that is Spring-aware, and allows you to navigate through the configurations via point-n-click on beans (references/names, to-and-from source code). <a href="http://www.jetbrains.com/idea/" rel="nofollow noreferrer">Intellij</a> works very well at this (version 7 and beyond, I think). I suspect Eclipse would do something similar.</li> <li>Revise <em>what</em> you're injecting <em>where</em>. You may want to refactor multiple bean injections into one composite or 'meta' bean, or a larger component. Or you may find that components you once thought you'd need to inject have never changed, or never demanded that injectability (for testing, implementing as strategies etc.)</li> </ol> <p>I used to work with a huge Spring installation, with hundreds (thousands?) of beans. Splitting the configurations up made life a lot more manageable, and simplified testing/creating standalone processes etc. But I think the Intellij Spring integration that came with Intellij made the most difference. Having a Spring-aware IDE is a major timesaver.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload